io.github.jeanlopezxyz/mcp-alertmanager
mcp-alertmanager
Is the io.github.jeanlopezxyz/mcp-alertmanager MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.
A Model Context Protocol (MCP) server for Prometheus Alertmanager
alive probed 2026-11-15 · unchanged since 2026-10-31
- Run it
- npx -y mcp-alertmanager@2.1.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- mcp-alertmanager v2.1.1
- Capabilities
- logging, tools
- Instructions
- none
- Of a 1M window
- 0.1 % of a 1M context window
- Count
- 1.3k tokens in Claude Opus 5.5, exact, measured 2026-10-31. With the Claude Code prefix mcp__…__ on each tool name: 1.4k. The o200k_base estimate is 689. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/jeanlopezxyz/mcp-alertmanager
- Registry
- active, updated 2026-02-03 · registry entry
- Changes
- 3 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.86×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| createSilence | 262 | 141 | 20 % |
| getAlerts | 234 | 126 | 18 % |
| getSilences | 113 | 61 | 9 % |
| getAlertHistory | 112 | 60 | 9 % |
| investigateAlert | 104 | 56 | 8 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.jcislo/moltalyzer-mcp · crashed on start
- Ragmir io.github.jcode-works/ragmir · alive
- Pincushion io.github.jcooley8/pincushion · alive
- Townspace / MapApp io.github.jdr377/mapapp-agent-connector · crashed on start
- io.github.jeanlopezxyz/mcp-prometheus · alive
- Verdict io.github.jeannicolasdavid1979/verdict-mcp · needs env
- Stock Images MCP io.github.jeanpfs/stock-images-mcp · alive
- io.github.jedanderson432/jedanderson-corpus-mcp · alive
Servers that mention prometheus.
- ai.getvda/kafka-and-postgres-monitoring-stack · newer protocol
- ai.getvda/postgres-kafka-prometheus-stack-generator · newer protocol
- ai.getvda/postgres-prometheus-stack-generator · newer protocol
- io.github.PrometheusAgency/bluesky-brand-monitor · needs auth
- io.github.PrometheusAgency/bluesky-followers-export · needs auth
- io.github.PrometheusAgency/bluesky-scraper · needs auth
- io.github.PrometheusAgency/eu-industrial-emissions · needs auth
- io.github.PrometheusAgency/eudr-parcel-screener · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-31 07:35 | alive | 99 ms | 12 | 1.3k | 689 |
| 2026-10-24 06:32 | alive | 76 ms | 12 | 689 | |
| 2026-10-17 06:16 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.