MCP Prometheus (yeonkyu-git/MCP-Prometheus-Loki) is an MCP server listed on the M8ven Trust Index. It scores 67 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
67/100
1 month ago

MCP Prometheus

An MCP server for Prometheus-based monitoring that enables users to query system metrics, resource usage, and PostgreSQL health across multiple environments. It supports both predefined diagnostic checks and custom PromQL execution for comprehensive server monitoring and troubleshooting.

→ yeonkyu-git/MCP-Prometheus-Loki· 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

yeonkyu-git

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: PROM_BEARER_TOKEN, LOKI_BEARER_TOKEN
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.
configPROM_URL3. fallback
🔐 secretPROM_BEARER_TOKEN
configPROM_TIMEOUT_SEC
configLOKI_URL2. fallback
🔐 secretLOKI_BEARER_TOKEN
configLOKI_TIMEOUT_SEC
configALERT_WARN_PCT
configALERT_CRIT_PCT
configALERT_SUSTAIN_MINUTES
configPROM_MAX_SAMPLES_PER_SERIES
configPROM_MAX_PARALLEL_CHECKS
configPROM_ENV_URLS{"prod":"http://...:9090","dev_test":"http://...:9090","dr":"http://...:9090"}
configLOKI_ENV_URLS{"prod":"http://...:3100","dev_test":"http://...:3100"}
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — get_alerts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_checks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_environments (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. 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

9/12 tool handlers declare input schemas (75%)

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

Tool handlers catch errors

Only 2/12 tool handlers wrap calls in try/catch (17%)

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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 6 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/yeonkyu-git/mcp-prometheus-loki)](https://m8ven.ai/mcp/yeonkyu-git/mcp-prometheus-loki)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8ef5336383320eca882b20be58ff1e9a32d7a635
code hash: 66175660f84ebe59e61de75b6d5e0bd4658d055b27246a7bea820d0a18692c03
verified: 8/6/2026, 3:14:27 PM
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