# @mikusnuz/npm-mcp

MCP server for npm package management — publish, version, search, audit, and more from your AI assistant

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.3.0
- **Author:** plumbug
- **License:** MIT
- **npm:** @mikusnuz/npm-mcp
- **Source:** https://github.com/mikusnuz/npm-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-13T23:16:24.185Z
- **Version scanned:** 1.3.0
- **CVEs:** none found by OSV at scan time

## Tools

39 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `publish` — Publish a package to the npm registry
- `stage` — Stage a package, inspect pending versions, download a tarball, or approve/reject a stage. Approval publishes the version; rejection removes the staged version. 
- `version` — Bump the package version
- `view` — View package information from the registry
- `search` — Search npm registry for packages
- `unpublish` — Remove a package version from the registry
- `deprecate` — Deprecate a version of a package
- `owner` — Manage package owners
- `dist-tag` — Manage distribution tags
- `pack` — Create a tarball from a package (preview what would be published)
- `whoami` — Check which npm user is currently authenticated. If not logged in, set NPM_TOKEN env var in MCP config.
- `init` — Initialize a new package.json
- `audit` — Run a security audit on the package
- `outdated` — Check for outdated packages in a project
- `ls` — List installed packages in a project
- `install` — Install packages in a project
- `uninstall` — Remove packages from a project
- `update` — Update packages in a project to their latest semver-compatible version
- `access` — Set or view access level on published packages
- `token` — Manage npm access tokens (list or revoke)
- `ping` — Check connectivity to the npm registry
- `bugs` — Get the bug tracker URL for a package
- `repo` — Get the repository URL for a package
- `docs` — Get the documentation URL for a package
- `diff` — Show diff between package versions or between local and registry
- `pkg` — Manage package.json fields programmatically
- `fund` — Show funding information for installed packages
- `dedupe` — Reduce duplication in the dependency tree
- `explain` — Explain why a package is installed (show dependency chain)
- `sbom` — Generate a Software Bill of Materials (SBOM) for a project
- `profile` — View or modify npm user profile settings
- `ci` — Clean install dependencies from lockfile (for CI environments)
- `run-script` — Run a script defined in package.json
- `doctor` — Run diagnostics to check npm environment health
- `cache` — Manage the npm cache
- `config` — View npm configuration (read-only for safety)
- `prune` — Remove extraneous packages not listed in package.json
- `link` — Symlink a local package for development
- `query` — Query installed packages using CSS-like selectors

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"npm\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@mikusnuz/npm-mcp\"\n      ],\n      \"env\": {\n        \"NPM_TOKEN\": \"<YOUR_NPM_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `NPM_TOKEN` — npm Token (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — mutates data; holds an api key.
- Floor 46, ceiling 46 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40mikusnuz%2Fnpm-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40mikusnuz%2Fnpm-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mikusnuz%2Fnpm-mcp
- HTML page: https://forgeregistry.com/registry/%40mikusnuz%2Fnpm-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.