Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ramkrsna/prometheus-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/ramkrsna/prometheus-mcp-server/server)<a href="https://agentmods.dev/mcp/ramkrsna/prometheus-mcp-server/server"><img src="https://agentmods.dev/badge/mcp/ramkrsna/prometheus-mcp-server/server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ramkrsna/prometheus-mcp-server/server"><img src="https://agentmods.dev/badge/mcp/ramkrsna/prometheus-mcp-server/server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
89% identical to prometheus-mcp-server — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "server": { "command": "npx", "args": [ "-y", "@prometheus-mcp/server" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A c908eb8c86a1
server is an MCP server published in the GitHub repository ramkrsna/prometheus-mcp-server (0 stars, last pushed 1y ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 89% identical to prometheus-mcp-server, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
monitor
BetterDB MCP server - Valkey observability for Claude Code and other MCP clients. Runs locally from the @betterdb/mcp npm package. Needs 3 environment variables to run.
prometheus-mcp-server
Model Context Protocol server for Prometheus queries and metrics. Runs locally from the prometheus-mcp-server npm package.
claude-flow
Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code. Runs locally from the @claude-flow/cli npm package. Needs 6 environment variables to run.
mcp
Real-time global intelligence across conflict, markets, energy, trade, shipping and cyber. 94 tools. Remote server at worldmonitor.app.
homelab-monitor
MCP server "homelab-monitor" as configured in SikamikanikoBG/homelab-monitor. Runs in Docker (docker.io/sikamikaniko123/homelab-monitor:0.14.2). Needs 2 environment variables to run.
mcp-telemetry-server
Streams live progress from mcp-telemetry-sdk-instrumented tools to any connected MCP client. Runs locally from the mcp-telemetry-server npm package.