io.github.CloudCorpRecords/metricwatch
metricwatch
Is the io.github.CloudCorpRecords/metricwatch MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.
Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client.
alive probed 2026-11-01
11tools
1.4ktokens in Claude Opus 5.5
0.7 %of Claude's 200k window
0.5×the median server
332 msto initialize
8 msto list tools
- Run it
- npx -y @reneturcios/metricwatch@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- metricwatch 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- 0.1 % of a 1M context window
- Count
- 1.4k tokens in Claude Opus 5.5, exact, measured 2026-11-01. With the Claude Code prefix mcp__…__ on each tool name: 1.5k. The o200k_base estimate is 742. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/metricwatch
- Registry
- active, updated 2026-11-01 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.87×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| search_logs | 241 | 129 | 17 % |
| query_timeseries | 220 | 118 | 16 % |
| list_metrics | 136 | 73 | 10 % |
| list_monitors | 116 | 62 | 8 % |
| get_metric_metadata | 108 | 58 | 8 % |
Compare this server with others.
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.