@pipeworx/repology

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/repology’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

Repology MCP — cross-distro package version aggregator. Tracks ~5 M package entries across Linux distributions, BSDs, language ecosystems, and other repos. Keyless.

Tools

• project(name) — every package across all repos for a project name
• problems(project) — outstanding maintenance problems for a project
• repositories() — list every repo Repology indexes (stats + status)
• maintainer(maintainer) — maintainer summary (e.g. [email protected])
• projects_search(start_name?, end_name?, search?, maintainer?, category?, in_repo?, not_in_repo?, count?) — paginate over projects

Data source

https://repology.org/api/v1/

Known issue

When invoked through the hosted Pipeworx gateway, repology often returns HTTP 522. The Cloudflare-Workers shared egress IPs appear to be throttled at repology.org’s Cloudflare edge. Direct browser/CLI calls to the same endpoint succeed. If you self-host this pack on a different egress (your own server, your laptop), the API is fully usable.

Tools

• project — All packages (per-repo) for one project name (e.g. “firefox”).
• problems — Outstanding maintenance problems for a project.
• repositories — List all package repositories indexed by Repology (distros, BSDs, language ecosystems, etc.) with their names, family, and active/total package counts.
• maintainer — Maintainer summary by canonical maintainer id (often email).
• projects_search — Paginate or filter Repology projects by name substring, maintainer, category, or repository membership; returns up to 200 project names per page with their per-repo version data.