Summary
Version questions answered by the registry, not by recollection.
Which version is current, what a version pulled in, and what changed since the one you are on are exactly the facts a model states confidently and gets a year out of date. This puts the npm registry behind them, including the changelog from the linked repo.
What it is
An MCP server over the public npm registry, exposing package and version data as structured tools so an assistant answers from registry.npmjs.org rather than from memory.
What you get
- The latest stable version of a package, and the complete list of every version published
- The manifest for one specific version — dependencies, license, engines and the rest
- All dist-tags (latest, beta, next and any others) and the versions they point at
- Release notes pulled from GitHub Releases, or CHANGELOG.md from the linked repository
- A yes-or-no check on whether a given package@version was ever published
- Package metadata beyond versions: description, author, license, homepage, maintainers, keywords, repository and README
Requirements
A recent Python, speaking MCP over stdio, so it drops into Claude Code, Claude Desktop, Cursor, Cline, Windsurf and Copilot Chat with one config entry. No API key — the npm registry data it reads is public.