Labsco
MCP SERVER

npm Registry MCP

by EinfacheEnte ↗

Answers npm questions without leaving the conversation: is this package maintained, does this version have CVEs, what changed between v4 and v5.

Package Registries & Dependency Supply Chain✓ Verified
Summary
Package decisions made in place.

Choosing a dependency normally means leaving the editor for four tabs: npm, GitHub, a CVE database, the changelog. All four answers are one call each here, which is what makes the comparison actually happen instead of getting skipped.

What it is

An MCP server over the npm registry, covering package discovery, version history, download statistics, vulnerability checks, side-by-side comparison, changelogs, dependents and READMEs.

What you get
  • Packages searched by keyword, with quality and maintenance scores
  • Full package details: description, latest version, license, maintainers, repository and dependencies
  • Every published version with its publish date
  • Download statistics over a period you choose
  • Known vulnerabilities for one specific version
  • Two packages compared side by side on downloads, maintenance, quality and dependencies
  • Release notes between two versions, falling back to CHANGELOG.md
  • Packages that depend on a given package, ranked by popularity
  • The full README of any package
Requirements

Node.js v18 or higher. npx handles the rest — nothing to clone or build, and no key.

Setup effort

One command — npx mcp-npm-registry