io.github.sbrunner-atx/contest-mcp
io.github.sbrunner-atx/contest-mcp
Is the io.github.sbrunner-atx/contest-mcp MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Log amateur-radio QSOs to N3FJP logging software over its TCP API.
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-11-13
error: No solution found when resolving dependencies cause: Because there is no version of contest-mcp==0.1.2 and you require contest-mcp==0.1.2, we can concl
- Run it
- uvx contest-mcp@0.1.2 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/sbrunner-atx/contest-mcp
- Registry
- deprecated, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.saviodamato/agentrank-mcp · needs mcp<2
- FPL Context io.github.sbanthia92/fpl-context-mcp · alive
- Second Read io.github.sbanthia92/second-read · alive
- whosaid io.github.sblattj/whosaid · alive
- io.github.sbrunner-atx/fldigi-mcp · alive
- io.github.sbrunner-atx/n3fjp-mcp · alive
- Serial Console MCP: AI for telecom equipment and any serial device io.github.sbrunner-atx/serial-console-mcp · alive
- io.github.sbrunner-atx/wsjtx-mcp · alive
Servers that mention contest.
- BASE167 com.base167/base167 · alive
- com.qronoplay/qronoplay · needs auth
- ink.writeflow/writeflow · alive
- Omniology io.github.omniologynow-rgb/mcp-server · alive
- QRvote org.qrvote/qrvote · needs auth
- BountyHunte.rs rs.bountyhunte/programs · not MCP
- PollUnit com.pollunit/mcp · needs auth
- io.github.qso-graph/n1mm-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
- No valid answer since 2026-10-16, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.