Is Elasticsearch MCP Server safe to use?

Elasticsearch MCP Server has an HVTrust score of 53.2/100 (Grade C), ranked #446 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Elasticsearch MCP Server?

Elasticsearch MCP Server scores 53.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 705 GitHub stars and is categorized under MCP Servers.

Elasticsearch MCP Server

elastic/mcp-server-elasticsearch

MCP Servers Rust Grade C Listed Apache-2.0

53.2/100

Rank #446 of 1308

Compare Elasticsearch MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-14 · 5d ago

Recent change

Rank +3

Is Elasticsearch MCP Server safe? Elasticsearch MCP Server scores 53.2/100 (Grade C), ranked #446 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 100% of recent commits are signed; last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#152 Scout MCP Local — 53.7 (C) → #153 SportIQ MCP — 53.4 (C) → #155 AirMCP — 53.2 (C) → #156 SearXNG HTTP MCP — 52.8 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-19

Rank Moved

Rank dropped 14 spots (#432 → #446)

2026-08-17

Rank Moved

Rank rose 12 spots (#442 → #430)

2026-08-13

Rank Moved

Rank dropped 16 spots (#413 → #429)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Elasticsearch MCP Server View MCP Servers Report missing data

51.6

Activity sub-score · out of 100

#154

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

705

Forks

146

Last Push

2026-08-14

5 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼14

was #432

Analysis

HVTrust Dimensions vs MCP Servers

53.2 / 100 · 100.0% confidence

Elasticsearch MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.6 / 25

5.6 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

3.5 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

11.7 / 20

0.7 below avg 12.4

AdoptionLog-scaled stars · package downloads

6.8 / 20

1.0 above avg 5.8

Activity Inputs

51.6 / 100

StarsRepository reach

17.1 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 8

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 5

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Elasticsearch MCP Server safe?

Public trust evidence for Elasticsearch MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Elasticsearch MCP Server publish package provenance?

No published build provenance is currently detected for Elasticsearch MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Elasticsearch MCP Server have an OpenSSF Scorecard?

Elasticsearch MCP Server has an OpenSSF Scorecard score of 4.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Elasticsearch MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does Elasticsearch MCP Server use?

Elasticsearch MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Elasticsearch MCP Server's commits signed?

100% of the last 100 commits to Elasticsearch MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Elasticsearch MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Elasticsearch MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

Maintain Elasticsearch MCP Server?

For maintainers

HVTrust scores Elasticsearch MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-19

Rank Moved

Rank dropped 14 spots (#432 → #446)

2026-08-17

Rank Moved

Rank rose 12 spots (#442 → #430)

2026-08-13

Rank Moved

Rank dropped 16 spots (#413 → #429)

2026-08-12

Rank Moved

Rank rose 13 spots (#426 → #413)

2026-08-10

Rank Moved

Rank dropped 20 spots (#408 → #428)

2026-08-08

Rank Moved

Rank dropped 101 spots (#306 → #407)

2026-07-15

Rank Moved

Rank dropped 16 spots (#260 → #276)

2026-07-14

Rank Moved

Rank dropped 12 spots (#248 → #260)

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Grade Changed

Trust grade D → C

2026-07-13

Rank Moved

Rank rose 85 spots (#333 → #248)

2026-07-13

HVTrust Changed

HVTrust up 41.4pts (11.4 → 52.8)

2026-07-13

Activity Score Changed

Activity score up 55pts (0 → 55)

2026-07-12

Newly Listed

First tracked at rank #333

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/elasticsearch-mcp-server.svg)](https://hvtracker.net/agents/elasticsearch-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/elasticsearch-mcp-server"><img src="https://hvtracker.net/badge/elasticsearch-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON