这是一个模型上下文协议 (MCP) 服务器，提供获取有关 npm 包的信息的功能。
软件包搜索：获取有关 npm 软件包详细信息的工具
热门软件包：列出 10 个最热门 npm 软件包的资源
Related MCP server: NPM Helper MCP
要通过Smithery自动为 Claude Desktop 安装 NPM MCP 服务器：
npx -y @smithery/cli install @mateusribeirocampos/npm-mcp-server --client claudenpm installnpm run buildnpm start对于开发：
npm run dev该服务器公开两个主要功能：
获取特定 npm 包的详细信息。该工具返回全面的包信息，包括：
包裹名字
最新版本
描述
作者信息
主页网址
存储库 URL
依赖项列表
使用示例：
const result = await server.tools.searchNpmPackage({ packageName: "react" });响应示例：
{
"name": "react",
"version": "18.2.0",
"description": "React is a JavaScript library for building user interfaces.",
"author": "Meta Open Source",
"homepage": "https://reactjs.org/",
"repository": {
"url": "https://github.com/facebook/react.git"
},
"dependencies": {
"loose-envify": "^1.1.0"
}
}列出 10 个最受欢迎的 npm 软件包，按受欢迎程度排序。列表中的每个软件包都包含：
包裹名字
描述
当前版本
资源 URI： npm://popular
响应示例：
[
{
"name": "lodash",
"description": "Lodash modular utilities",
"version": "4.17.21"
},
// ... more packages
]该 MCP 服务器可以与 AI 模型集成，以：
安装前获取软件包信息
比较不同的包版本
分析依赖关系
寻找热门替代品
获取快速包裹摘要
TypeScript
模型上下文协议 SDK
节点获取
佐德
| Name | Required | Description | Default |
|---|---|---|---|
| packageName | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0searchNpmPackageScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'searchNpmPackage' has a distinct and clear purpose by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'searchNpmPackage' uses a consistent verb_noun pattern with no deviations to evaluate.
A single tool is too few for a server named 'NPM MCP Server', which implies broader npm-related functionality. This feels thin and incomplete for the apparent scope of npm package management.
The tool set is severely incomplete for an npm server. Only search functionality is provided, with no coverage for install, view, publish, update, or other essential npm operations, leading to significant gaps.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Dive into the world of npm with our NPM Package Info MCP. Access crucial metadata about any npm
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…