MCP server for the npm registry — search packages, check versions, vulnerabilities, download stats and more
MCP server for the npm registry — search packages, check versions, vulnerabilities, download stats and more. Exposed over MCP by the npm registry mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
An MCP (Model Context Protocol) server that gives Claude direct access to the npm registry — search packages, check versions, audit vulnerabilities, compare libraries and more, all without leaving your conversation.
Everything the assistant can do here goes through one of these:
search_packages — Search npm by keyword with quality and maintenance scoresget_package_info — Full details — license, maintainers, dependencies, size, downloadsget_package_versions — Full version history with publish datesget_download_stats — Download counts over any period (day / week / month / year)check_vulnerabilities — Known CVEs for a specific package versioncompare_packages — Side-by-side comparison of two packagesget_changelog — Release notes between two versions, falls back to CHANGELOG.mdget_package_readme — Full README for any package or specific versionPrerequisites — The Prerequisites tool exposed by this serverThe server ships on npm as mcp-npm-registry, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Npm Registry MCP's toolset — search_packages, get_package_info, get_package_versions and 6 more — is a fair guide to whether it matches your workflow. It is maintained by einfacheente; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_packages | Search npm by keyword with quality and maintenance scores |
| get_package_info | Full details — license, maintainers, dependencies, size, downloads |
| get_package_versions | Full version history with publish dates |
| get_download_stats | Download counts over any period (day / week / month / year) |
| check_vulnerabilities | Known CVEs for a specific package version |
| compare_packages | Side-by-side comparison of two packages |
| get_changelog | Release notes between two versions, falls back to CHANGELOG.md |
| get_package_readme | Full README for any package or specific version |
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"npm-registry": {
"command": "npx",
"args": ["mcp-npm-registry"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.