io.github.mikusnuz/npm
NPM · @MIKUSNUZ/NPM-MCP · SCANNED SEP 22
MCP server for npm package management — publish, version, search, audit, and more
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. 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
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2084 tokens (~53/item across 39 items; 38 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 39 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.mikusnuz/npm MCP server?
io.github.mikusnuz/npm runs locally as an npm package, launched with npx -y @mikusnuz/npm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mikusnuz/npm-mcp
claude mcp add mikusnuz-npm -- npx -y @mikusnuz/npm-mcp
{
"mcpServers": {
"mikusnuz-npm": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/npm-mcp"
]
}
}
} {
"servers": {
"mikusnuz-npm": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/npm-mcp"
]
}
}
} codex mcp add mikusnuz-npm -- npx -y @mikusnuz/npm-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mikusnuz-npm": {
"type": "local",
"command": [
"npx",
"-y",
"@mikusnuz/npm-mcp"
],
"enabled": true
}
}
} openclaw mcp add mikusnuz-npm --command npx --arg -y --arg @mikusnuz/npm-mcp
mcp_servers:
mikusnuz-npm:
command: "npx"
args: ["-y", "@mikusnuz/npm-mcp"] {
"McpServers": {
"mikusnuz-npm": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mikusnuz/npm-mcp"
]
}
}
} assistant mcp add mikusnuz-npm -t stdio -c npx -a -y @mikusnuz/npm-mcp
{
"mcpServers": {
"mikusnuz-npm": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
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 22 Sept 2026 · Analysed npm/@mikusnuz/npm-mcp@1.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
access ~94
Set or view access level on published packages
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| level | string | – | Access level (for set action) |
| otp | string | – | One-time password for 2FA |
| package | string | – | Package name |
| permission | string | – | Permission level (for grant action) |
| team | string | – | Team name in org:team format (for grant/revoke) |
No output schema declared.
No examples provided.
audit ~61
Run a security audit on the package
| Name | Type | Req | Description |
|---|---|---|---|
| fix | boolean | – | Automatically fix vulnerabilities |
| level | string | – | Minimum vulnerability level to report |
| path | string | yes | Absolute path to the package directory |
| production | boolean | – | Only audit production dependencies |
No output schema declared.
No examples provided.
bugs ~25
Get the bug tracker URL for a package
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name |
No output schema declared.
No examples provided.
cache ~49
Manage the npm cache
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: clean (clear cache), verify (check integrity), ls (list contents) |
| force | boolean | – | Force clean (required for clean action) |
No output schema declared.
No examples provided.
ci ~31
Clean install dependencies from lockfile (for CI environments)
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
config ~52
View npm configuration (read-only for safety)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: list (show all config), get (get specific key) |
| key | string | – | Config key to get (required for get action) |
No output schema declared.
No examples provided.
dedupe ~41
Reduce duplication in the dependency tree
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview changes without making them |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
deprecate ~74
Deprecate a version of a package
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Deprecation message (empty string to undeprecate) |
| otp | string | – | One-time password for 2FA |
| package | string | yes | Package@version range (e.g. pkg@<1.0.0) |
No output schema declared.
No examples provided.
diff ~114
Show diff between package versions or between local and registry
| Name | Type | Req | Description |
|---|---|---|---|
| diffNameOnly | boolean | – | Only show file names that changed |
| package | string | – | Package spec for comparison (e.g. pkg@1.0.0..pkg@2.0.0) |
| path | string | – | Absolute path to local package (compares local vs registry) |
| specs | array | – | Two package specs to compare (e.g. ['pkg@1.0.0', 'pkg@2.0.0']) |
No output schema declared.
No examples provided.
dist-tag ~53
Manage distribution tags
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| package | string | yes | Package name (for add: pkg@version) |
| tag | string | – | Tag name (required for add/rm) |
No output schema declared.
No examples provided.
docs ~24
Get the documentation URL for a package
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name |
No output schema declared.
No examples provided.
doctor ~15
Run diagnostics to check npm environment health
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain ~42
Explain why a package is installed (show dependency chain)
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name to explain |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
fund ~38
Show funding information for installed packages
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | – | Specific package to check |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
init ~43
Initialize a new package.json
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the directory |
| scope | string | – | Scope for the package (e.g. @myorg) |
No output schema declared.
No examples provided.
install ~95
Install packages in a project
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview install without making changes |
| global | boolean | – | Install globally |
| packages | array | – | Package names to install (empty = install all from package.json) |
| path | string | yes | Absolute path to the package directory |
| saveDev | boolean | – | Save as devDependency |
| saveExact | boolean | – | Save exact version instead of semver range |
No output schema declared.
No examples provided.
link ~46
Symlink a local package for development
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | – | Package name to link (omit to link current dir globally) |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
ls ~90
List installed packages in a project
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Show all packages, not just top-level |
| depth | number | – | Dependency tree depth (default: 0) |
| global | boolean | – | List global packages |
| package | string | – | Specific package to look for |
| path | string | yes | Absolute path to the package directory |
| production | boolean | – | Only show production dependencies |
No output schema declared.
No examples provided.
outdated ~48
Check for outdated packages in a project
| Name | Type | Req | Description |
|---|---|---|---|
| global | boolean | – | Check global packages |
| long | boolean | – | Show extended information |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
owner ~58
Manage package owners
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| otp | string | – | One-time password for 2FA |
| package | string | yes | Package name |
| user | string | – | Username (required for add/rm) |
No output schema declared.
No examples provided.
pack ~48
Create a tarball from a package (preview what would be published)
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | List files without creating tarball |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
ping ~14
Check connectivity to the npm registry
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pkg ~81
Manage package.json fields programmatically
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| field | string | yes | Field name (e.g. 'name', 'scripts.build', 'keywords') |
| path | string | yes | Absolute path to the package directory |
| value | string | – | Value to set (required for set action, use JSON for objects/arrays) |
No output schema declared.
No examples provided.
profile ~76
View or modify npm user profile settings
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| field | string | – | Profile field to get or set (e.g. email, fullname, homepage) |
| otp | string | – | One-time password for 2FA |
| value | string | – | Value to set (required for set action) |
No output schema declared.
No examples provided.
prune ~53
Remove extraneous packages not listed in package.json
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview changes without making them |
| path | string | yes | Absolute path to the package directory |
| production | boolean | – | Remove devDependencies |
No output schema declared.
No examples provided.
publish ~80
Publish a package to the npm registry
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Access level for scoped packages |
| dryRun | boolean | – | Run publish without actually publishing |
| otp | string | – | One-time password for 2FA |
| path | string | yes | Absolute path to the package directory |
| tag | string | – | Dist-tag (default: latest) |
No output schema declared.
No examples provided.
query ~54
Query installed packages using CSS-like selectors
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the package directory |
| selector | string | yes | CSS-like dependency selector (e.g. ':root > .prod', '.dev', '#lodash') |
No output schema declared.
No examples provided.
repo ~24
Get the repository URL for a package
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name |
No output schema declared.
No examples provided.
run-script ~59
Run a script defined in package.json
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Arguments to pass to the script |
| path | string | yes | Absolute path to the package directory |
| script | string | – | Script name to run (omit to list available scripts) |
No output schema declared.
No examples provided.
sbom ~62
Generate a Software Bill of Materials (SBOM) for a project
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | SBOM format (default: cyclonedx) |
| path | string | yes | Absolute path to the package directory |
| production | boolean | – | Only include production dependencies |
No output schema declared.
No examples provided.
search ~35
Search npm registry for packages
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20) |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
token ~55
Manage npm access tokens (list or revoke)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| otp | string | – | One-time password for 2FA |
| token | string | – | Token ID to revoke (required for revoke) |
No output schema declared.
No examples provided.
uninstall ~48
Remove packages from a project
| Name | Type | Req | Description |
|---|---|---|---|
| global | boolean | – | Uninstall from global |
| packages | array | yes | Package names to uninstall |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
unpublish ~68
Remove a package version from the registry
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force unpublish (required for entire package) |
| otp | string | – | One-time password for 2FA |
| package | string | yes | Package name with optional version (e.g. pkg@1.0.0) |
No output schema declared.
No examples provided.
update ~72
Update packages in a project to their latest semver-compatible version
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview updates without making changes |
| global | boolean | – | Update global packages |
| packages | array | – | Specific packages to update (empty = update all) |
| path | string | yes | Absolute path to the package directory |
No output schema declared.
No examples provided.
version ~68
Bump the package version
| Name | Type | Req | Description |
|---|---|---|---|
| bump | string | yes | Version bump type |
| noGitTag | boolean | – | Skip git tag creation |
| path | string | yes | Absolute path to the package directory |
| preid | string | – | Prerelease identifier (e.g. alpha, beta) |
No output schema declared.
No examples provided.
view ~51
View package information from the registry
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Specific field to view (e.g. versions, dist-tags) |
| package | string | yes | Package name (e.g. react, @scope/pkg) |
No output schema declared.
No examples provided.
whoami ~31
Check which npm user is currently authenticated. If not logged in, set NPM_TOKEN env var in MCP config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.mikusnuz/npm MCP server?
io.github.mikusnuz/npm is an MCP server listed in the public MCP registry as io.github.mikusnuz/npm. MCP server for npm package management, publish, version, search, audit, and more. This page covers its npm package (@mikusnuz/npm-mcp).
Is the io.github.mikusnuz/npm MCP server safe to use?
io.github.mikusnuz/npm scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mikusnuz/npm MCP server expose?
io.github.mikusnuz/npm exposes 38 tools: publish, version, view, search, unpublish, and 33 more. Their descriptions and schemas cost roughly 2,072 tokens of context every time the server is loaded.
Is the io.github.mikusnuz/npm MCP server still maintained?
io.github.mikusnuz/npm is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mikusnuz/npm MCP server under?
io.github.mikusnuz/npm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.