updated 2026-10-11 08:08 UTC

Cr7258 Elasticsearch MCP Server

Repository

A Model Context Protocol (MCP) server implementation that provides Elasticsearch and OpenSearch interaction.

MCP Servers Python Listed Apache-2.0

Is Cr7258 Elasticsearch MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 54%
Last push today
Advisories None known
Compare Cr7258 Elasticsearch MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Cr7258 Elasticsearch MCP Server scores 58.3/100 (Grade C), ranked #705 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 54% of recent commits are signed; no published advisory affects its latest release (elasticsearch-mcp-server); last pushed 2026-10-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cr7258 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 Cr7258 Elasticsearch MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/cr7258/elasticsearch-mcp-server, Apache-2.0, last pushed 2026-10-11. 54% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review2
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 9
    Branch-Protection 0
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 9

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: elasticsearch-mcp-server 2.1.4. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 3.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Cr7258 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 Cr7258 Elasticsearch MCP Server compares in MCP Servers

  1. #384 Google Health MCP 58.4 +0.1
  2. #385 Drawio MCP 58.4 +0.1
  3. #386 Cr7258 Elasticsearch MCP Server 58.3 this agent
  4. #387 MCP Console Automation 58.3 ±0
  5. #388 Computer Use 58.3 ±0

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

Where the 58.3 comes from

HVTrust dimensions vs the MCP Servers average

58.3 / 100 · 100.0% confidence

Cr7258 Elasticsearch MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.4 / 25
2.0 below 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.4 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
15.1 / 20
2.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
10.6 / 20
3.2 above 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-11
Rank Moved
Rank rose 40 spots (#745 → #705)
2026-10-10
Rank Moved
Rank rose 29 spots (#774 → #745)
2026-10-09
Rank Moved
Rank dropped 11 spots (#763 → #774)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/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 Cr7258 Elasticsearch MCP Server View MCP Servers Report missing data
58.2
Activity sub-score · out of 100
#386
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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

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

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
312
Forks
66
Last Push
2026-10-11
today
Commits (4 wk)
5
Downloads (7d)
3,088
pypi
HN mentions (30d)
—
Open Issues
8
Rank Change
▲40
was #745

Analysis

Activity Inputs

58.2 / 100
StarsRepository reach
15.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
8.5 / 20

Common questions about Cr7258 Elasticsearch MCP Server

Cr7258 Elasticsearch MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Cr7258 Elasticsearch MCP Server publish package provenance?
No published build provenance is currently detected for Cr7258 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 Cr7258 Elasticsearch MCP Server have an OpenSSF Scorecard?
Cr7258 Elasticsearch MCP Server has an OpenSSF Scorecard score of 4.6/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 Cr7258 Elasticsearch MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Cr7258 Elasticsearch MCP Server use?
Cr7258 Elasticsearch MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cr7258 Elasticsearch MCP Server's commits signed?
54% of the last 100 commits to Cr7258 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
Cr7258 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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Cr7258 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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Cr7258 Elasticsearch MCP Server?

For maintainers

HVTrust scores Cr7258 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 25Grade 4Score 3HVTrust 3Listed 2Scorecard 1Delisted 1MCP 1
2026-10-11
Rank Moved
Rank rose 40 spots (#745 → #705)
2026-10-10
Rank Moved
Rank rose 29 spots (#774 → #745)
2026-10-09
Rank Moved
Rank dropped 11 spots (#763 → #774)
2026-10-02
Grade Changed
Trust grade D → C
2026-10-02
Rank Moved
Rank rose 197 spots (#959 → #762)
2026-10-02
HVTrust Changed
HVTrust up 6.3pts (49.8 → 56.1)
2026-10-02
Activity Score Changed
Activity score up 14pts (42 → 56)
2026-10-01
Grade Changed
Trust grade C → D
2026-09-30
Rank Moved
Rank dropped 14 spots (#942 → #956)
2026-09-25
Rank Moved
Rank dropped 12 spots (#919 → #931)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 168 spots (#1084 → #916)
2026-09-23
HVTrust Changed
HVTrust up 27.9pts (22.6 → 50.5)
2026-09-22
Newly Listed
First tracked at rank #1084
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-15
Rank Moved
Rank dropped 70 spots (#831 → #901)
2026-09-15
Activity Score Changed
Activity score down 6pts (50 → 44)
2026-09-14
Rank Moved
Rank dropped 16 spots (#815 → #831)
2026-09-12
Rank Moved
Rank dropped 12 spots (#798 → #810)
2026-09-11
Rank Moved
Rank dropped 10 spots (#788 → #798)
2026-09-09
Rank Moved
Rank dropped 14 spots (#769 → #783)
2026-09-07
Rank Moved
Rank dropped 42 spots (#722 → #764)
2026-09-06
Rank Moved
Rank dropped 14 spots (#708 → #722)
2026-09-05
Rank Moved
Rank dropped 74 spots (#634 → #708)
2026-09-04
Rank Moved
Rank dropped 24 spots (#610 → #634)
2026-09-03
Rank Moved
Rank dropped 39 spots (#571 → #610)
2026-09-01
Scorecard Added
OSSF Scorecard: 3.6/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 485 spots (#1063 → #578)
2026-09-01
HVTrust Changed
HVTrust up 22.5pts (31.5 → 54.0)
2026-08-31
Rank Moved
Rank dropped 33 spots (#1030 → #1063)
2026-08-30
Rank Moved
Rank dropped 56 spots (#974 → #1030)
2026-08-29
Rank Moved
Rank dropped 48 spots (#926 → #974)
2026-08-28
Rank Moved
Rank dropped 38 spots (#888 → #926)
2026-08-27
Rank Moved
Rank dropped 28 spots (#860 → #888)
2026-08-26
Rank Moved
Rank dropped 110 spots (#750 → #860)
2026-08-16
Activity Score Changed
Activity score up 5pts (55 → 60)
2026-08-10
Rank Moved
Rank dropped 39 spots (#706 → #745)
2026-08-08
Newly Listed
First tracked at rank #708
GitHub → PyPI: elasticsearch-mcp-server

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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