Prometheus MCP
MCP server for LLMs to interact with Prometheus
Is Prometheus MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Prometheus MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Prometheus MCP scores 61.4/100 (Grade C), ranked #659 of 1374 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 7.1/10; 56% of recent commits are signed; last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How Prometheus MCP 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.
- Raise the OSSF Scorecard from 7.1 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +4.0 → 65.4 B · #297 of 778
- Sign every commit56% signed today +2.2 → 63.6 C · #329 of 778
Chain of custody
Scanners check what the code says. This traces who ships Prometheus MCP 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.
-
Source Partly signed
github.com/prometheus/prometheus-mcp, Apache-2.0, last pushed 2026-11-08. 56% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 7.1/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:
- Code Review7
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies9
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 5CI-Tests 10CII-Best-Practices 0Code-Review 7Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 9SAST 0Security-Policy 9Signed-Releases 0Token-Permissions 10Vulnerabilities 7 -
Published packages None
No registry package. Prometheus MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-08-26 OSSF Scorecard: 7.3/10
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 Prometheus MCP’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.
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 Prometheus MCP compares in MCP Servers
- #360 MySQL MCP Server 61.7 +0.3
- #361 Xiaohongshu MCP 61.5 +0.1
- #362 Prometheus MCP 61.4 this agent
- #363 MCP Document Reader 61.3 −0.1
- #364 Laravel MCP Companion 61.1 −0.3
Bars show each HVTrust score; the tick marks Prometheus MCP’s 61.4.
Where the 61.4 comes from
HVTrust dimensions vs the MCP Servers average
61.4 / 100 · 100.0% confidencePrometheus MCP MCP Servers average (778 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
61.7 / 100Common questions about Prometheus MCP
Does Prometheus MCP publish package provenance?
Does Prometheus MCP have an OpenSSF Scorecard?
Is Prometheus MCP actively maintained?
What license does Prometheus MCP use?
Are Prometheus MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Prometheus MCP'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.
Maintain Prometheus MCP?
For maintainers
HVTrust scores Prometheus MCP 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/prometheus-mcp)
<a href="https://hvtracker.net/agents/prometheus-mcp"><img src="https://hvtracker.net/badge/prometheus-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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