{
  "markdown": "# @pipeworx/repology\n\n[Repology](https://repology.org) MCP — cross-distro package version aggregator. Tracks ~5 M package entries across Linux distributions, BSDs, language ecosystems, and other repos. Keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `project(name)` — every package across all repos for a project name\n- `problems(project)` — outstanding maintenance problems for a project\n- `repositories()` — list every repo Repology indexes (stats + status)\n- `maintainer(maintainer)` — maintainer summary (e.g. `john@example.com`)\n- `projects_search(start_name?, end_name?, search?, maintainer?, category?, in_repo?, not_in_repo?, count?)` — paginate over projects\n\n## Data source\n\n`https://repology.org/api/v1/`\n\n## Known issue\n\nWhen invoked through the hosted Pipeworx gateway, repology often returns\nHTTP 522. The Cloudflare-Workers shared egress IPs appear to be throttled\nat repology.org's Cloudflare edge. Direct browser/CLI calls to the same\nendpoint succeed. If you self-host this pack on a different egress (your\nown server, your laptop), the API is fully usable.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"repology\": {\n      \"url\": \"https://gateway.pipeworx.io/repology/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/repology/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Repology data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3190,
  "sha": "122ff00d68a5eab22102c3315f93217d9b793b4066db02be40e6006cdcb7d2ea",
  "repo_slug": "pipeworx-io/mcp-repology",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_repology_29b46e97/readme"
}