io.github.rog0x/log
mcp-log-tools
Is the io.github.rog0x/log MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
Log parse, filter, analyze for AI agents
alive probed 2026-11-14 · unchanged since 2026-10-30
5tools
1.7ktokens in Claude Opus 5.5
0.8 %of Claude's 200k window
0.7×the median server
277 msto initialize
10 msto list tools
- Run it
- npx -y @rog0x/mcp-log-tools@1.0.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- mcp-log-tools 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- 0.2 % of a 1M context window
- Count
- 1.7k tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 1.7k. The o200k_base estimate is 934. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/rog0x/mcp-log-tools
- Registry
- active, updated 2026-03-22 · 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.77×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| filter_logs | 453 | 256 | 27 % |
| format_logs | 400 | 226 | 24 % |
| parse_logs | 331 | 187 | 20 % |
| log_stats | 246 | 139 | 15 % |
| analyze_logs | 223 | 126 | 13 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.rog0x/i18n · alive
- io.github.rog0x/image · alive
- io.github.rog0x/json · alive
- io.github.rog0x/lint · alive
- io.github.rog0x/markdown · alive
- io.github.rog0x/math · crashed on start
- io.github.rog0x/network · alive
- io.github.rog0x/npm · alive
Servers that mention rog0x.
- io.github.rog0x/git · alive
- io.github.rog0x/crypto · alive
- io.github.rog0x/perf · alive
- io.github.rog0x/schema · alive
- io.github.rog0x/env · alive
- io.github.rog0x/file · alive
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.