F
licenseNot graded
qualityC
maintenanceProvides a tool to fetch npm package information via MCP. Enables AI agents to retrieve structured package details using the getNpmPackageInfo tool.
-
npm-registry-mcp-server
by yuchen814
Related Servers
Alternatives to npm-registry-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server to search npm packages, view details, compare, check downloads, and inspect dependencies.632 npmMIT
- AlicenseAqualityDmaintenanceMCP server that searches npm packages and returns live registry data without an API key. Supports package search, detailed info, and side-by-side comparison of packages.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching npm packages, retrieving package details and version histories, and fetching download statistics through the npm Registry API.1 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides a tool to fetch npm package information via the Model Context Protocol.8-
- AlicenseAqualityBmaintenanceFetches npm package READMEs, metadata, and search results for MCP-compatible AI clients.311 npmMIT
TDQS
A4.2/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct primary purposes: fetching metadata for a package (or specific version) versus listing available versions and dist-tags. While get_npm_package_metadata with allVersions can also return version information, the descriptions make the intended use of each tool unambiguous.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern with snake_case: get_npm_package_metadata and list_npm_package_versions. The verbs 'get' and 'list' are appropriate for their respective operations, and the naming is predictable and uniform.
Tool Count3/5
With only 2 tools, the server feels slightly thin for an npm registry surface, as it could reasonably include operations like search or package file downloads. However, the narrow read-only metadata focus makes this count defensible and not excessive.
Completeness4/5
The server covers the core read-only operations for npm package metadata: retrieving metadata (with version, tag, or range options) and listing available versions. Minor gaps exist, such as no direct search or readme retrieval, but these are not essential for the stated purpose of querying package information.
Maintenance
ActivitySlowing
ResponsivenessNo issues