NPMScan
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
Reviews
No review yet. Used NPMScan? Be the first to help others choose.What it does
NPMScan is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://npmscan.com/api/mcpstreamable-http
In Claude Code: claude mcp add --transport http npmscan https://npmscan.com/api/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"npmscan": {
"url": "https://npmscan.com/api/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE NPMScan answered an MCP connection on 14 Nov 2026 and introduced itself as npmscan 3.1.3 (MCP protocol 2025-06-18).
23 tools offered to AI assistants
search_packages· Search the npm registry by name or keywords. Each result includes its current weekly/monthly download counts, dependentsCount (how many other npm packages depend on it), topPackagesRank (position among npmscan's own top-100k-by-downloads snget_package· Fetch npm registry metadata for a package: latest version, install scripts (preinstall/postinstall are a key risk signal), maintainers, license, recent version history, weekly downloads, GitHub stars, TypeScript support, days since last pubget_package_version· Fetch registry metadata for one exact version of a package (dependencies, install scripts, tarball) AND check that exact version against OSV.dev for known vulnerabilities — isVulnerable/highestSeverity give a direct answer, and each findingget_maintainer_profile· Given an npm username, returns every package npm's own maintainer:<username> search index currently returns for that account (registry.npmjs.org's /-/v1/search — the public registry API has no dedicated 'list packages by maintainer' endpoinquery_vulnerabilities· Query OSV.dev for known vulnerabilities affecting an npm package, optionally scoped to one exact version (e.g. to check whether a version pinned in a lockfile is safe). Returns isVulnerable and highestSeverity as a direct answer, plus eachbatch_query_vulnerabilities· Check a whole npm dependency inventory against OSV.dev in one call: pass `packages: [{name, version?}]`, or raw package.json / package-lock / yarn.lock / pnpm-lock / CycloneDX / SPDX content via `content`. Large inventories are chunked autoget_latest_advisories· Browse recently published npm security advisories and known-malicious-package findings. Three disjoint sources, selected via type: "reviewed" (default) is GitHub's curated, mostly CVE-backed advisories; "malware" is GitHub's own known-malicget_cve· Look up authoritative NIST NVD data for one exact CVE ID (e.g. "CVE-2026-2950"), or browse/search NVD by keyword, CVSS severity, CWE, or a publication-date range. Every result is enriched with CISA KEV status (`kev`, non-null only if this Canalyze_install_script· Statically scans a package's preinstall/install/postinstall/prepare lifecycle scripts AND the file(s) they reference — fetched directly from the published tarball, not just the command string in package.json — against npmscan's documented ranalyze_transitive_dependencies· Walk one or more root packages' dependency trees (e.g. a package.json "dependencies" section) up to `maxDepth` levels (default 2, max 3) and check every resolved package@version against OSV.dev, so vulnerabilities several levels down stillcheck_package_provenance· Checks whether a package version was published with npm's own Sigstore-backed publish provenance (`npm publish --provenance`), and cross-checks that provenance against reality rather than just reporting its presence. Three checks: (1) parsecheck_maintainer_changes· Reconstruct who has controlled an npm package and when, straight from the packument (each version records the maintainer list at publish time and who ran `npm publish`). Use it for the 'who controls this package, and did that change recentl
Show 11 more
check_maintainer_blast_radius· Given an npm username, lists the packages npm's maintainer:<username> search index returns for that account and looks for a tight cluster of packages whose latest version was published within a short rolling window of each other — the shapecheck_license_compliance· Given a list of packages (name + optional exact version or semver range — e.g. straight from a package.json "dependencies" object) and an optional allow/deny license policy, resolves each package's declared SPDX license and reports a complidiff_dependencies· Compare two snapshots of a package.json, package-lock.json (v1-v3), yarn.lock (classic or Berry) or pnpm-lock.yaml (e.g. before/after a PR; formats can differ) and report added, removed and changed packages. Lockfiles cover the full resolveprioritize_remediation· Rank vulnerability findings other tools already returned (batch_query_vulnerabilities, query_vulnerabilities, analyze_transitive_dependencies, diff_dependencies...) by what to fix first. Pass up to 200 `{packageName, cveId?, severity?, advisimulate_dependency_upgrade· Before running npm install, check whether upgrading a package from a current to a target version is safe. Pass `packageName` + `currentVersion` + `targetVersion` (omit target for "latest"), or `packages: [...]` (1-100) to check many in onesuggest_alternative· Given a package that looks deprecated, vulnerable, abandoned, or suspicious, suggest better-maintained alternatives in the same category. This tool first checks the source package's own latest-version health (deprecation, latest-version OSVcompare_packages· Compare 2-5 candidate packages for the same job (e.g. "axios vs got vs node-fetch") side by side and get a deterministic pick. More than 5 names is rejected, never truncated; duplicate names are rejected. Use search_packages first if you haaudit_github_repository· Audit a GitHub repository's npm dependencies from its URL — no pasted files needed. Fetches package.json plus the first lockfile found (pnpm-lock.yaml, then package-lock.json, then yarn.lock) from the default branch (or `ref`), and detectsget_remediation_playbook· Maps a finding's `rule` value from analyze_install_script, check_maintainer_changes, or check_package_provenance to the matching human-authored incident-response playbook (the same content published at /docs/playbooks) and returns its concrgenerate_sbom· Given the same inputs batch_query_vulnerabilities accepts — either a flat {packages:[...]} list, or raw package.json / lockfile / CycloneDX JSON / SPDX JSON content via `content` — emits a spec-valid CycloneDX 1.6 or SPDX 2.3 JSON documentenrich_npm_audit· Given the raw output of `npm audit --json` (npm 7+'s `{vulnerabilities: {...}}` format, or legacy npm 6's `{advisories: {...}}`), parses it directly — no need to re-paste package.json/lockfile content — and runs it through the same remove-n
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://npmscan.com/api/mcp | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Version | 3.1.2 | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Website | https://npmscan.com | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Repository | https://github.com/salemalem/npmscan-mcp-plugin | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 19h ago |
Change history
- VERSION10 Oct 20263.1.1 → 3.1.2
- VERSION10 Oct 20263.1.0 → 3.1.1
- VERSION09 Oct 20261.0.0 → 3.1.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is NPMScan still online?
Free alerts · no account▲ 0Do you run NPMScan? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about NPMScan
How do I connect NPMScan?
Use the hosted endpoint https://npmscan.com/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does NPMScan offer?
When Electra Index connected on 14 Nov 2026, it listed 23 tools: search_packages, get_package, get_package_version, get_maintainer_profile, query_vulnerabilities, batch_query_vulnerabilities, get_latest_advisories, get_cve and more. The full list is in "Live check" above.
Is NPMScan online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.