Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mikusnuz/npm

NPM · @MIKUSNUZ/NPM-MCP

MCP server for npm package management — publish, version, search, audit, and more

Available components

0 this week 79 Trust /100

Last scanned (19 hours ago)

Scores higher than 63% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 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 32 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 2411 tokens (~56/item across 43 items; 42 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
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 43 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 19 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 16 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 14 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 10 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −5
    • Provenance: pass → unverified ▼ security
Diagnostics

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 21 Nov 2026 · Analysed npm/@mikusnuz/npm-mcp@1.4.0

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 42 exposed · ~2,399 tokens

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 →

Tool Tokens
access ~94

Set or view access level on published packages

NameTypeReqDescription
actionstringyesAction to perform
levelstring–Access level (for set action)
otpstring–One-time password for 2FA
packagestring–Package name
permissionstring–Permission level (for grant action)
teamstring–Team name in org:team format (for grant/revoke)

No output schema declared.

No examples provided.

approve-scripts ~58

Approve reviewed dependency install scripts, pinned by npm to installed versions. Only changes policy; does not run scripts. Requires npm 12+. Never approve packages without reviewing them.

NameTypeReqDescription
packagesarrayyes–
pathstringyes–

No output schema declared.

No examples provided.

audit ~61

Run a security audit on the package

NameTypeReqDescription
fixboolean–Automatically fix vulnerabilities
levelstring–Minimum vulnerability level to report
pathstringyesAbsolute path to the package directory
productionboolean–Only audit production dependencies

No output schema declared.

No examples provided.

bugs ~25

Get the bug tracker URL for a package

NameTypeReqDescription
packagestringyesPackage name

No output schema declared.

No examples provided.

cache ~49

Manage the npm cache

NameTypeReqDescription
actionstringyesAction: clean (clear cache), verify (check integrity), ls (list contents)
forceboolean–Force clean (required for clean action)

No output schema declared.

No examples provided.

ci ~31

Clean install dependencies from lockfile (for CI environments)

NameTypeReqDescription
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

config ~52

View npm configuration (read-only for safety)

NameTypeReqDescription
actionstringyesAction: list (show all config), get (get specific key)
keystring–Config key to get (required for get action)

No output schema declared.

No examples provided.

dedupe ~41

Reduce duplication in the dependency tree

NameTypeReqDescription
dryRunboolean–Preview changes without making them
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

deny-scripts ~46

Deny install scripts for named dependencies across all versions. Only changes package.json policy. Requires npm 12+.

NameTypeReqDescription
packagesarrayyes–
pathstringyes–

No output schema declared.

No examples provided.

deprecate ~74

Deprecate a version of a package

NameTypeReqDescription
messagestringyesDeprecation message (empty string to undeprecate)
otpstring–One-time password for 2FA
packagestringyesPackage@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

NameTypeReqDescription
diffNameOnlyboolean–Only show file names that changed
packagestring–Package spec for comparison (e.g. pkg@1.0.0..pkg@2.0.0)
pathstring–Absolute path to local package (compares local vs registry)
specsarray–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

NameTypeReqDescription
actionstringyesAction to perform
packagestringyesPackage name (for add: pkg@version)
tagstring–Tag name (required for add/rm)

No output schema declared.

No examples provided.

docs ~24

Get the documentation URL for a package

NameTypeReqDescription
packagestringyesPackage 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)

NameTypeReqDescription
packagestringyesPackage name to explain
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

fund ~38

Show funding information for installed packages

NameTypeReqDescription
packagestring–Specific package to check
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

init ~43

Initialize a new package.json

NameTypeReqDescription
pathstringyesAbsolute path to the directory
scopestring–Scope for the package (e.g. @myorg)

No output schema declared.

No examples provided.

install ~130

Install packages in a project

NameTypeReqDescription
allowScriptsarray–Explicitly reviewed packages allowed to run install scripts during a global install (npm 12+). For project installs use approve-scripts instead.
dryRunboolean–Preview install without making changes
globalboolean–Install globally
packagesarray–Package names to install (empty = install all from package.json)
pathstringyesAbsolute path to the package directory
saveDevboolean–Save as devDependency
saveExactboolean–Save exact version instead of semver range

No output schema declared.

No examples provided.

link ~46

Symlink a local package for development

NameTypeReqDescription
packagestring–Package name to link (omit to link current dir globally)
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

ls ~90

List installed packages in a project

NameTypeReqDescription
allboolean–Show all packages, not just top-level
depthnumber–Dependency tree depth (default: 0)
globalboolean–List global packages
packagestring–Specific package to look for
pathstringyesAbsolute path to the package directory
productionboolean–Only show production dependencies

No output schema declared.

No examples provided.

outdated ~48

Check for outdated packages in a project

NameTypeReqDescription
globalboolean–Check global packages
longboolean–Show extended information
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

owner ~58

Manage package owners

NameTypeReqDescription
actionstringyesAction to perform
otpstring–One-time password for 2FA
packagestringyesPackage name
userstring–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)

NameTypeReqDescription
dryRunboolean–List files without creating tarball
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

pending-scripts ~35

List dependencies whose install scripts need review without changing package.json. Requires npm 12 or later.

NameTypeReqDescription
pathstringyes–

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 ~80

Manage package.json fields programmatically

NameTypeReqDescription
actionstringyesAction to perform
fieldstringyesField name (e.g. 'name', 'scripts.build', 'keywords')
pathstringyesAbsolute path to the package directory
value––JSON value to set; strings are literal strings, objects/arrays are accepted directly

No output schema declared.

No examples provided.

profile ~76

View or modify npm user profile settings

NameTypeReqDescription
actionstringyesAction to perform
fieldstring–Profile field to get or set (e.g. email, fullname, homepage)
otpstring–One-time password for 2FA
valuestring–Value to set (required for set action)

No output schema declared.

No examples provided.

prune ~53

Remove extraneous packages not listed in package.json

NameTypeReqDescription
dryRunboolean–Preview changes without making them
pathstringyesAbsolute path to the package directory
productionboolean–Remove devDependencies

No output schema declared.

No examples provided.

publish ~80

Publish a package to the npm registry

NameTypeReqDescription
accessstring–Access level for scoped packages
dryRunboolean–Run publish without actually publishing
otpstring–One-time password for 2FA
pathstringyesAbsolute path to the package directory
tagstring–Dist-tag (default: latest)

No output schema declared.

No examples provided.

query ~54

Query installed packages using CSS-like selectors

NameTypeReqDescription
pathstringyesAbsolute path to the package directory
selectorstringyesCSS-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

NameTypeReqDescription
packagestringyesPackage name

No output schema declared.

No examples provided.

run-script ~59

Run a script defined in package.json

NameTypeReqDescription
argsarray–Arguments to pass to the script
pathstringyesAbsolute path to the package directory
scriptstring–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

NameTypeReqDescription
formatstring–SBOM format (default: cyclonedx)
pathstringyesAbsolute path to the package directory
productionboolean–Only include production dependencies

No output schema declared.

No examples provided.

search ~35

Search npm registry for packages

NameTypeReqDescription
limitnumber–Max results (default 20)
querystringyesSearch query

No output schema declared.

No examples provided.

stage ~154

Stage a package, inspect pending versions, download a tarball, or approve/reject a stage. Approval publishes the version; rejection removes the staged version. Requires an npm CLI supporting npm stage.

NameTypeReqDescription
accessstring–Access for staged publish
actionstringyes–
dryRunboolean–Preview staged publish without uploading
otpstring–2FA code for approving or rejecting a stage
packagestring–Optional package spec to filter the list
pathstring–Package directory for publish; destination directory for download
stageIdstring–Required for view, download, approve, and reject
tagstring–Dist-tag for staged publish

No output schema declared.

No examples provided.

token ~55

Manage npm access tokens (list or revoke)

NameTypeReqDescription
actionstringyesAction to perform
otpstring–One-time password for 2FA
tokenstring–Token ID to revoke (required for revoke)

No output schema declared.

No examples provided.

uninstall ~48

Remove packages from a project

NameTypeReqDescription
globalboolean–Uninstall from global
packagesarrayyesPackage names to uninstall
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

unpublish ~68

Remove a package version from the registry

NameTypeReqDescription
forceboolean–Force unpublish (required for entire package)
otpstring–One-time password for 2FA
packagestringyesPackage 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

NameTypeReqDescription
dryRunboolean–Preview updates without making changes
globalboolean–Update global packages
packagesarray–Specific packages to update (empty = update all)
pathstringyesAbsolute path to the package directory

No output schema declared.

No examples provided.

version ~68

Bump the package version

NameTypeReqDescription
bumpstringyesVersion bump type
noGitTagboolean–Skip git tag creation
pathstringyesAbsolute path to the package directory
preidstring–Prerelease identifier (e.g. alpha, beta)

No output schema declared.

No examples provided.

view ~51

View package information from the registry

NameTypeReqDescription
fieldstring–Specific field to view (e.g. versions, dist-tags)
packagestringyesPackage 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.

Install

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

# add to Claude Code
claude mcp add mikusnuz-npm -- npx -y @mikusnuz/npm-mcp
Common questions

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 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 42 tools: publish, stage, version, view, search, and 37 more. Their descriptions and schemas cost roughly 2,399 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 21 November 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.

What did VerifyMCP test on the io.github.mikusnuz/npm MCP server?

VerifyMCP ran 15 checks on io.github.mikusnuz/npm, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mikusnuz/npm: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.