Elasticsearch MCP Server Solution (TocharianOU/elasticsearch-mcp) is an MCP server listed on the M8ven Trust Index. It scores 62 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Caution

62/100

Elasticsearch MCP Server Solution

Item: Elasticsearch MCP Server Solution
Rating: 62
Author: M8ven

Enables comprehensive interaction with Elasticsearch APIs through natural language queries, specifically optimized for security analysis, threat detection, incident investigation, and compliance monitoring with advanced machine learning capabilities for anomaly detection.

→ TocharianOU/elasticsearch-mcp · listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

TocharianOU

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

⚠️

Known vulnerabilities in dependencies: 3 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 2 credentials: ES_API_KEY, ES_PASSWORD

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

esql_query

execute_es_api

Execute any Elasticsearch API endpoint directly

get_mappings

Get field mappings for Elasticsearch index(es) with intelligent analysis and filtering

get_shards

Get detailed shard information with intelligent health analysis and optimization recommendations

list_data_streams

List and analyze Elasticsearch data streams with health monitoring and rollover tracking

list_indices

List all available Elasticsearch indices with smart filtering and analysis for large index sets

es_search

Perform an Elasticsearch search with the provided query DSL. Highlights are always enabled.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.22.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.22.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.22.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

🔐 secretES_API_KEYElasticsearch API key for authentication No

configES_CA_CERTPath to custom CA certificate for Elasticsearch SSL/TLS No

🔐 secretES_PASSWORDElasticsearch password for basic authentication No

configES_URLYour Elasticsearch instance URL Yes

configES_USERNAMEElasticsearch username for basic authentication No

configMAX_TOKEN_CALL

configMCP_HTTP_HOSTHTTP server host (when using HTTP transport) localhost Any valid host

configMCP_HTTP_PORTHTTP server port (when using HTTP transport) 3000 1-65535

configMCP_TRANSPORTTransport mode selection stdio stdio, http

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — esql_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_es_api (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_mappings (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/7 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.22.0 (high), @modelcontextprotocol/sdk@1.22.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Verified](https://m8ven.ai/badge/mcp/tocharianou/elasticsearch-mcp?variant=verified)](https://m8ven.ai/mcp/tocharianou/elasticsearch-mcp)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: a31090607f1a87bc5c9820af866a7e5e1a687cb5

code hash: 2a1866f7290ed9e3411b25afb6c89c67e8cd68e9ffc33866e1b0b7d683bfdbbe

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client