이는 npm 패키지에 대한 정보를 가져오는 기능을 제공하는 MCP(Model Context Protocol) 서버입니다.
패키지 검색 : npm 패키지에 대한 자세한 정보를 가져오는 도구
인기 패키지 : 가장 인기 있는 10개의 npm 패키지를 나열하는 리소스
Related MCP server: NPM Helper MCP
Smithery를 통해 Claude Desktop에 NPM MCP 서버를 자동으로 설치하려면:
지엑스피1
npm installnpm run buildnpm start개발을 위해:
npm run dev서버는 두 가지 주요 기능을 제공합니다.
특정 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"
}
}가장 인기 있는 npm 패키지 10개를 인기순으로 정렬하여 나열합니다. 목록의 각 패키지에는 다음이 포함됩니다.
패키지 이름
설명
현재 버전
리소스 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…