これは、npm パッケージに関する情報を取得する機能を提供するモデル コンテキスト プロトコル (MCP) サーバーです。
パッケージ検索: 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サーバーは主に 2 つの機能を公開します。
特定のnpmパッケージに関する詳細情報を取得します。このツールは、以下を含む包括的なパッケージ情報を返します。
パッケージ名
最新バージョン
説明
著者情報
ホームページURL
リポジトリ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 モデルと統合して次のことが可能になります。
インストール前にパッケージ情報を取得する
異なるパッケージバージョンを比較する
依存関係を分析する
人気の代替品を探す
クイックパッケージ概要を取得する
タイプスクリプト
モデルコンテキストプロトコル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…