Asking for "HTTP clients for Rust" resolves to Crates.io without you naming it, and the response tells the agent which ecosystem to stay in for follow-ups — which is what stops a conversation drifting between npm and PyPI results. Coverage is even across the six except for one gap stated up front: PyPI has no official downloads API, so download figures are not available there.
A package-registry lookup server covering npm, PyPI, RubyGems, Crates.io, Packagist and Hex. It works out which ecosystem you mean from the question, or you can name one.
- Package search with the ecosystem detected from the wording of the query, or set explicitly when you want control
- Package details enriched with download numbers and GitHub information — stars, forks, license — and optionally the README inline
- The README on its own, truncated at a length you choose
- Usage examples extracted out of the README, so you get the calling pattern without reading the whole document
- Version listings, bounded by a limit or a date, and the dependency list for a given version
- Download statistics over a period you pick — available for every ecosystem except PyPI, which publishes no official downloads API
- Specific packages compared across ecosystems when you want to weigh, say, an npm library against a PyPI one
No account and no key for the registries themselves. Node.js v18.17 or newer; run it with npx -y packagelens-mcp@latest over stdio, from the npm package packagelens-mcp, currently 0.1.11. It makes live requests to the six registries and to GitHub when tools are called. GITHUB_TOKEN is optional and only raises the GitHub rate limit, from 60 requests an hour unauthenticated to 5000 with a token.
One command — npx -y packagelens-mcp@latest