io.github.qso-graph/n1mm-mcp
n1mm-mcp
Is the io.github.qso-graph/n1mm-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-14.
N1MM Logger+ MCP server. Live contest state: QSOs, bandmap, score, rate, multipliers.
alive probed 2026-11-15 · unchanged since 2026-11-14
12tools
3.4ktokens in Claude Opus 5.5
1.7 %of Claude's 200k window
1.4×the median server
8.5 sto initialize
736 msto list tools
- Run it
- uvx n1mm-mcp@0.5.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- n1mm-mcp 0.5.0
- Capabilities
- logging, prompts, resources, tools
- Instructions
- 179 characters
- Of a 1M window
- 0.3 % of a 1M context window
- Count
- 3.4k tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 3.5k. The o200k_base estimate is 2.0k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/qso-graph/n1mm-mcp
- Registry
- active, updated 2026-11-14 · 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.74×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| n1mm_contacts | 448 | 258 | 13 % |
| n1mm_pileup | 366 | 211 | 11 % |
| n1mm_bandmap | 359 | 207 | 11 % |
| n1mm_clock | 342 | 197 | 10 % |
| n1mm_so2r | 339 | 195 | 10 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.qso-graph/js8call-mcp · alive
- io.github.qso-graph/jt-mcp · alive
- io.github.qso-graph/lotw-mcp · alive
- io.github.qso-graph/meteor-mcp · alive
- io.github.qso-graph/netlogger-mcp · alive
- io.github.qso-graph/omiss-mcp · alive
- io.github.qso-graph/pota-mcp · alive
- io.github.qso-graph/qrz-mcp · 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.