mshegolev/prometheus-mcp (mshegolev/prometheus-mcp) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 21 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
69/100

mshegolev/prometheus-mcp

MCP server for Prometheus metrics and observability. Give Claude (or any MCP-capable agent) read access to your Prometheus instance — query metrics with PromQL, inspect active alerts, and explore scrape targets without leaving the conversation. Tools: prometheus_list_metrics, prometheus_query, prometheus_query_range, prometheus_list_alerts, prometheus_list_targets.

→ mshegolev/prometheus-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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 pushwhy connect →

Who stands behind it

mshegolev

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
✅
21 tools verified — handlers match their declared behaviour
21 read-only tools verified — handlers contain no write/delete/exec
✅
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 4 credentials: ALERTMANAGER_TOKEN, ALERTMANAGER_PASSWORD, PROMETHEUS_TOKEN, PROMETHEUS_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configPROMETHEUS_MCP_CONFIG
configALERTMANAGER_URL
🔐 secretALERTMANAGER_TOKEN
configALERTMANAGER_USERNAME
🔐 secretALERTMANAGER_PASSWORD
configALERTMANAGER_SSL_VERIFY
configPROMETHEUS_CACHE_TTL
configPROMETHEUS_URLYes — Prometheus server URL, e.g. https://prometheus.example.com (no trailing slash)
🔐 secretPROMETHEUS_TOKENNo — Bearer token (takes precedence over Basic auth)
configPROMETHEUS_USERNAMENo — HTTP Basic auth username
🔐 secretPROMETHEUS_PASSWORDNo — HTTP Basic auth password
configPROMETHEUS_SSL_VERIFYNo true Set false for self-signed certificates
configPROMETHEUS_TIMEOUT
configPROMETHEUS_MAX_RESPONSE_BYTES
// quality suggestions

All four hints declared on every tool

1/21 tools missing one or more hints — federation_list_instances (missing: destructiveHint, openWorldHint). 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

20/21 tool handlers declare input schemas (95%)

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

Tool handlers catch errors

20/21 tool handlers wrap calls in try/catch (95%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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 Score](https://m8ven.ai/badge/mcp/mshegolev/prometheus-mcp)](https://m8ven.ai/mcp/mshegolev/prometheus-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 99de357283989ce9f0cb7af242a3138bf66b00d5
code hash: 9a07f9c73da5d29ea05c1ab792437f72b84fb685e6a46bb4f65f4c173a59a8e6
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