io.github.tschoonj/repology-mcp-server
Repology API Server
Is the io.github.tschoonj/repology-mcp-server MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-10-31.
MCP server that provides access to Repology package repository data
needs mcp<2 probed 2026-11-14 · unchanged since 2026-10-31
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-10-31.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' repology-mcp-server@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- Repology API Server 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/tschoonj/repology-mcp-server
- Registry
- active, updated 2025-09-29 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| list_projects | 453 | 40 % |
| search_projects | 255 | 23 % |
| get_maintainer_problems | 166 | 15 % |
| get_repository_problems | 131 | 12 % |
| get_project | 123 | 11 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- OMEM io.github.troybrandonc-bit/omem · alive
- io.github.truecallerabreham/mcp-server-digitalocean · crashed on start
- vibatchium io.github.trueoriginlabs/vibatchium · alive
- io.github.trycoin-ai/agentrisk · needs args
- io.github.tschoonj/xraylib-mcp-server · needs mcp<2
- OpenRouter io.github.tsilva/mcp-openrouter · alive
- io.github.tspicer/amazon_ads_mcp · needs env
- io.github.tsutera09/tempo · alive
Servers that mention repology or repository or provides.
- Repology io.github.pipeworx-io/repology · alive
- io.github.mrfentmen/repology-mcp · alive
- ai.docuwriter/docuwriter · needs auth
- ai.seltz/seltz-ai-seltz-mcp · needs auth
- ai.thoughtbox.api/thoughts · needs auth
- ai.tickettailor/mcp · needs auth
- ai.smithery/anirbanbasu-pymcp · not found
- ai.smithery/brandonbosco-sigao-scf-mcp · not found
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:41 | needs mcp<2 | 1.4 s | 5 | 2.0k | 1.1k |
| 2026-10-17 06:20 | 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 package imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'