io.github.alisaitteke/npm-mcp
NPM · @ALISAITTEKE/NPM-MCP · SCANNED AUG 4
MCP server for npm package management, security analysis, and compatibility checking
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (115 of 119), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (115 of 119), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 186 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 706 tokens (~47/item across 15 items; 12 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @alisaitteke/npm-mcp
claude mcp add alisaitteke-npm-mcp -- npx -y @alisaitteke/npm-mcp
codex mcp add alisaitteke-npm-mcp -- npx -y @alisaitteke/npm-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alisaitteke-npm-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@alisaitteke/npm-mcp"
],
"enabled": true
}
}
} openclaw mcp add alisaitteke-npm-mcp --command npx --arg -y --arg @alisaitteke/npm-mcp
mcp_servers:
alisaitteke-npm-mcp:
command: "npx"
args: ["-y", "@alisaitteke/npm-mcp"] {
"mcpServers": {
"alisaitteke-npm-mcp": {
"command": "npx",
"args": [
"-y",
"@alisaitteke/npm-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Aug 26 +1
- Security disclosure: fail → unverified ▼ functional
- 2 Aug 26 +51
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −6
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 31 Jul 26 +20
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −47
- Malware scan: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Jul 26 53
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Aug 2026 · Analysed npm/@alisaitteke/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 115 packages
115 packages in the resolved dependency tree · 102 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
analyze_bundle_size ~51
Analyze bundle size impact: minified, gzipped sizes, tree-shaking support, recommendations
| Name | Type | Req | Description |
|---|---|---|---|
| packageName | string | yes | Name of the package |
| version | string | — | Specific version (optional) |
No output schema declared.
No examples provided.
analyze_capabilities ~64
Analyze package capabilities: ESM/CJS support, TypeScript, platforms (Node/Browser/Deno), exports, build tools
| Name | Type | Req | Description |
|---|---|---|---|
| packageName | string | yes | Name of the package to analyze |
| version | string | — | Specific version (optional, defaults to latest) |
No output schema declared.
No examples provided.
analyze_npx_command ~78
Analyze and validate an npx command before execution (security check)
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | — | Command arguments (optional) |
| command | string | yes | Package to analyze (e.g., "create-react-app" or "[email protected]") |
| timeout | number | — | Timeout in milliseconds (default: 30000) |
No output schema declared.
No examples provided.
analyze_quality ~34
Evaluate package quality metrics including maintenance, popularity, and sustainability
| Name | Type | Req | Description |
|---|---|---|---|
| packageName | string | yes | Name of the package to analyze |
No output schema declared.
No examples provided.
audit_security ~45
Check package for known security vulnerabilities and get recommendations
| Name | Type | Req | Description |
|---|---|---|---|
| packageName | string | yes | Name of the package to audit |
| version | string | — | Specific version to audit (optional) |
No output schema declared.
No examples provided.
check_compatibility ~57
Analyze compatibility of a package with existing project dependencies
| Name | Type | Req | Description |
|---|---|---|---|
| existingDependencies | object | yes | Existing package.json dependencies |
| packageName | string | yes | Name of the package to check |
| version | string | — | Version or version range |
No output schema declared.
No examples provided.
compare_packages ~45
Compare multiple packages side-by-side (features, size, popularity, maintenance, TypeScript support)
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | yes | Array of package names to compare (2-5 packages) |
No output schema declared.
No examples provided.
compare_versions ~51
Compare different versions of a package and analyze breaking changes
| Name | Type | Req | Description |
|---|---|---|---|
| fromVersion | string | yes | Starting version |
| packageName | string | yes | Name of the package |
| toVersion | string | yes | Target version |
No output schema declared.
No examples provided.
find_similar_packages ~57
Find similar/alternative packages based on keywords and functionality
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Number of results (default: 5, max: 10) |
| packageName | string | yes | Name of the package to find alternatives for |
No output schema declared.
No examples provided.
generate_quick_start ~68
Generate ready-to-use code examples for a package (installation, basic usage, framework-specific examples)
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | — | Target framework (auto-detect if not specified) |
| packageName | string | yes | Name of the package |
| version | string | — | Specific version (optional) |
No output schema declared.
No examples provided.
get_package_details ~53
Get detailed information about a specific npm package including versions, dependencies, and repository info
| Name | Type | Req | Description |
|---|---|---|---|
| packageName | string | yes | Name of the package |
| version | string | — | Specific version (optional, defaults to latest) |
No output schema declared.
No examples provided.
search_packages ~56
Search npm registry for packages by name or keywords with popularity ranking
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of results (default: 10, max: 50) |
| query | string | yes | Search query (package name or keywords) |
No output schema declared.
No examples provided.