updated 2026-10-11 04:08 UTC

Elasticsearch MCP Server

Repository Website
MCP Servers Rust Listed Apache-2.0

Is Elasticsearch MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.5 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare Elasticsearch MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Elasticsearch MCP Server scores 53.5/100 (Grade C), ranked #866 of 1371 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-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Elasticsearch MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Elasticsearch MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/elastic/mcp-server-elasticsearch, Apache-2.0, last pushed 2026-10-10. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection5
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 5
    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

  3. Published packages None

    No registry package. Elasticsearch MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Elasticsearch MCP Server.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Elasticsearch MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Elasticsearch MCP Server compares in MCP Servers

  1. #479 GPU MCP Server 53.5 ±0
  2. #480 Opencage Geocoding MCP 53.5 ±0
  3. #481 Elasticsearch MCP Server 53.5 this agent
  4. #482 Doom MCP 53.5 ±0
  5. #483 Ocm MCP Server 53.4 −0.1

Bars show each HVTrust score; the tick marks Elasticsearch MCP Server’s 53.5.

Where the 53.5 comes from

HVTrust dimensions vs the MCP Servers average

53.5 / 100 · 100.0% confidence

Elasticsearch MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.6 / 25
in line with avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
11.9 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
6.9 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-02
Rank Moved
Rank rose 27 spots (#871 → #844)
2026-09-23
Rank Moved
Rank dropped 530 spots (#307 → #837)
2026-09-21
Rank Moved
Rank rose 531 spots (#830 → #299)
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
52.3
Activity sub-score · out of 100
#481
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 →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
717
Forks
158
Last Push
2026-10-10
yesterday
Commits (4 wk)
0?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
10
Rank Change
▼7
was #859

Analysis

Activity Inputs

52.3 / 100
StarsRepository reach
17.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.2 / 20

Common questions about Elasticsearch MCP Server

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 1 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

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
Rank 27
2026-10-02
Rank Moved
Rank rose 27 spots (#871 → #844)
2026-09-23
Rank Moved
Rank dropped 530 spots (#307 → #837)
2026-09-21
Rank Moved
Rank rose 531 spots (#830 → #299)
2026-09-14
Rank Moved
Rank rose 10 spots (#830 → #820)
2026-09-11
Rank Moved
Rank dropped 14 spots (#806 → #820)
2026-09-08
Rank Moved
Rank dropped 13 spots (#785 → #798)
2026-09-07
Rank Moved
Rank dropped 31 spots (#754 → #785)
2026-09-06
Rank Moved
Rank dropped 14 spots (#740 → #754)
2026-09-05
Rank Moved
Rank dropped 60 spots (#680 → #740)
2026-09-04
Rank Moved
Rank dropped 28 spots (#652 → #680)
2026-09-03
Rank Moved
Rank dropped 32 spots (#620 → #652)
2026-09-02
Rank Moved
Rank dropped 27 spots (#593 → #620)
2026-09-01
Rank Moved
Rank dropped 17 spots (#576 → #593)
2026-08-31
Rank Moved
Rank dropped 31 spots (#545 → #576)
2026-08-29
Rank Moved
Rank dropped 27 spots (#518 → #545)
2026-08-27
Rank Moved
Rank dropped 11 spots (#498 → #509)
2026-08-26
Rank Moved
Rank dropped 60 spots (#438 → #498)
2026-08-24
Rank Moved
Rank dropped 16 spots (#426 → #442)
2026-08-22
Rank Moved
Rank rose 17 spots (#445 → #428)
2026-08-19
Rank Moved
Rank dropped 13 spots (#432 → #445)
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)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.5 Grade C
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.4 · Raw JSON