by tjhop · MCP Server · ★ 51
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
docker run --rm -i ghcr.io/tjhop/prometheus-mcp-server:latest --prometheus.url "https://$yourPrometheus:9090"
docker run --rm -i -e PROMETHEUS_MCP_SERVER_PROMETHEUS_URL="https://$yourPrometheus:9090" ghcr.io/tjhop/prometheus-mcp-server:latest
Taken from the project's README on GitHub.
None of the 44 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 44 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours.
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 51 |
| Forks | 16 |
| Language | Go |
| Category | MCP Server |
| License | Apache-2.0 |
| Quality Score | 64/100 |
| Open Issues | 5 |
| Last Updated | 2026-06-20 |
| Created | 2025-05-02 |
| Platforms | go, mcp |
| Est. Tokens | ~22k |
Prometheus MCP Server About This is an MCP server to allow LLMs to interact with a running Prometheus instance via the API to do things like generate and execute promql queries, list and analyze metrics, etc. Demos and Examples Asking Claude to Investigate Slow Queries The prompt used was: querying my metrics is slow, can you help me figure out why?
Explore other popular mcp server tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 44 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: