Opensearch (PyPI) MCP Server

opensearch-mcp-server PyPI v2.1.3

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP Server for interacting with Elasticsearch and OpenSearch

View on PyPI ↗ Raw report (JSON) ↗

Trust grade

98/100

Last scanned 2026-08-25 get badge →

Trust

A · 98/100

Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.

Capability

Minimal

Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.

Coverage

Source

How much the scan could actually inspect. Shallow coverage is stated, never hidden.

A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

Points	Adoption-risk factor
−2	publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

low Shell/command execution in packaging/dev tooling (tests/e2e/containers/conftest.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/e2e/containers/conftest.py:171`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: arents[3] process = subprocess.Popen( [ sys.executable, "-m", "src.serve

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/e2e/containers/conftest.py

low Shell/command execution in packaging/dev tooling (tests/e2e/k8s/conftest.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/e2e/k8s/conftest.py:38`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: imeout=300): return subprocess.run( command, input=input_text, text=True, capture_ou

Location: server tests/e2e/k8s/conftest.py

Tools 20

Each tool and what it can reach — statically extracted from the published source.

analyze_textno sensitive capability
create_data_streamno sensitive capability
create_indexno sensitive capability
delete_aliasno sensitive capability
delete_by_queryno sensitive capability
delete_data_streamno sensitive capability
delete_documentno sensitive capability
delete_indexno sensitive capability
general_api_requestno sensitive capability
get_aliasno sensitive capability

Show 10 more tools ↓

get_cluster_healthno sensitive capability
get_cluster_statsno sensitive capability
get_data_streamno sensitive capability
get_documentno sensitive capability
get_indexno sensitive capability
index_documentno sensitive capability
list_aliasesno sensitive capability
list_indicesno sensitive capability
put_aliasno sensitive capability
search_documentsno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

Version	Score	Findings	Engine	Scanned
`v2.1.3` latest	A 98/100	2	1.13.0	2026-08-25
`v2.1.2`	A 98/100	2	1.12.1	2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/opensearch-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/opensearch-mcp-server)

HTML

<a href="https://mcptrustchecker.com/registry/opensearch-mcp-server"><img src="https://mcptrustchecker.com/registry/opensearch-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/opensearch-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan opensearch-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Opensearch 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

Opensearch (PyPI) PyPI

opensearch-mcp

Add your description here

Developer Tools Score 98/100 0 findings Cap. Minimal

Opensearch (minpeter) Source verified npm

opensearch-mcp

Zero-config web search and page fetch MCP backed by @minpeter/opensearch

Web, Search & Scraping Score 94/100 1 finding 30/wk Cap. High

Opensearch (PyPI) PyPI

mcp-server-opensearch

Web, Search & Scraping Score 87/100 0 findings Cap. Minimal

More in Web, Search & Scraping

Agent Ip Remote

https://agent-ip.biodnd.com/sse

Agent IP: MCP server with patents search tools

Web, Search & Scraping Score 100/100 0 findings Cap. Minimal

Agentalmanac Source verified npm

agentalmanac-mcp

MCP server for searching the Agent Almanac — the public catalog of 9,000+ Model Context Protocol servers. Find, install, and discover MCP servers from inside Claude Desktop, Cursor, Continue, Zed, or any MCP-aware agent.

Web, Search & Scraping Score 100/100 0 findings 55/wk Cap. Minimal

Agentery Remote

https://agentery.com/api/mcp

Search agents & MCP servers by capability, with daily-observed pricing, liveness and market data.

Web, Search & Scraping Score 100/100 0 findings Cap. Minimal

Agentic Terminal Directory Remote

https://mcp.agenticterminal.ai/mcp

Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.

Web, Search & Scraping Score 100/100 0 findings Cap. Minimal

Airframeai Client Source verified npm

@airframeai/mcp-client

Airframe MCP Client - Connect agents to Airframe's product intelligence