NPMScan
OnlineDetect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
What it can do: 23 tools
search_packagesread-onlySearch 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-get_packageread-onlyFetch 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,get_package_versionread-onlyFetch 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 answget_maintainer_profileread-onlyGiven 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 byquery_vulnerabilitiesread-onlyQuery 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 direcbatch_query_vulnerabilitiesread-onlyCheck 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 inventorget_latest_advisoriesread-onlyBrowse 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 GitHget_cveread-onlyLook 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`, nonanalyze_install_scriptread-onlyStatically 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 npanalyze_transitive_dependenciesread-onlyWalk 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 severacheck_package_provenanceread-onlyChecks 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. Thrcheck_maintainer_changesread-onlyReconstruct 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 didcheck_maintainer_blast_radiusread-onlyGiven 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 eacheck_license_complianceread-onlyGiven 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 licensediff_dependenciesread-onlyCompare 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 coprioritize_remediationread-onlyRank 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, cvesimulate_dependency_upgraderead-onlyBefore 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) tsuggest_alternativeread-onlyGiven 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 (deprecationcompare_packagesread-onlyCompare 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_packaudit_github_repositoryread-onlyAudit 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 (orget_remediation_playbookread-onlyMaps 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) agenerate_sbomread-onlyGiven 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 SPDenrich_npm_auditread-onlyGiven 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 throu
Connect it
claude mcp add --transport http npmscan https://npmscan.com/api/mcpSettings → Connectors → Add custom connector
URL: https://npmscan.com/api/mcp{
"mcpServers": {
"npmscan": {
"url": "https://npmscan.com/api/mcp"
}
}
}{
"servers": {
"npmscan": {
"type": "http",
"url": "https://npmscan.com/api/mcp"
}
}
}Questions
What does NPMScan do?
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups It exposes 23 tools to AI assistants.
What tools does NPMScan provide?
23 tools, including search_packages, get_package, get_package_version, get_maintainer_profile, query_vulnerabilities, batch_query_vulnerabilities, get_latest_advisories, get_cve, analyze_install_script, analyze_transitive_dependencies, check_package_provenance, check_maintainer_changes….
How do I connect NPMScan to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://npmscan.com/api/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does NPMScan require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is NPMScan online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes NPMScan?
@salemalem on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.
Similar in Developer Tools
-
Google DeveloperknowledgeOnlineOfficialPopular
Provides access to Google's public developer documentation.
-
Hugging FaceOnlineOfficialPopular
Connect to Hugging Face Hub and thousands of Gradio AI Applications
-
Visa Developer Center MCP ServerOnline · sign-in requiredOfficialPopularNew
Search Visa Developer docs and retrieve OpenAPI specs for Visa product APIs to build integrations.
-
BitlyOnline · sign-in requiredOfficialPopular
Shorten links, generate QR codes, and track performance across your Bitly account.
-
Remote Desktop CommanderOnline · sign-in requiredOfficial
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
-
Avalara ClassificationOnline · sign-in requiredOfficial
Classify, validate & verify HS codes and access tariff compliance data for cross-border trade