elasticsearch-mcp-server
PyPI
v2.1.2
Published by an unidentified publisher — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
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 the deduction.
In the server's implementation (`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: subprocess.Popen(
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
In the server's implementation (`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: subprocess.run(
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/k8s/conftest.py
"elasticsearch-mcp-server" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package elasticsearch-mcp-server
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.2 latest |
A 98/100 | 3 | 1.5.0 | 2026-07-22 |
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.
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 elasticsearch-mcp-server --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →
Elastic’s official MCP server: search indices and inspect mappings from an assistant.
Security scan results for the Elasticsearch (octodet) MCP server.
Security scan results for the Elasticsearch (tocharianou) MCP server.
Security scan results for the Elasticsearch (RajwardhanShinde) MCP server.
Security scan results for the Elasticsearch (hlos-ai) MCP server.
Security scan results for the Elasticsearch (manojkumarg) MCP server.
Security scan results for the 3gpp Mcp Charging MCP server.
Security scan results for the 4o Mini Search MCP server.
Security scan results for the A11y Color Contrast MCP server.
Security scan results for the A2asearch MCP server.
Security scan results for the Access Calibre MCP server.
Security scan results for the Activitypub MCP server.