What is the main functional difference between NPMScan and Next Devtools MCP?

NPMScan is categorized under Developer Tools and uses an install path we have not confirmed yet. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick NPMScan for developer tools work and Next Devtools MCP for developer tools.

How do I install NPMScan or Next Devtools MCP in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. NPMScan has no confirmed install command yet — follow its own setup instructions.

Are NPMScan and Next Devtools MCP free to use, or do they require API keys?

NPMScan is listed as free. Auth: no auth required. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both NPMScan and Next Devtools MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add npmscan-2 and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, NPMScan has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 8 views, 0 installs and 828 GitHub stars.

NPMScan vs Next Devtools MCP — MCP Server Comparison

NPMScan vs Next Devtools MCP — MCP Server Comparison | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	N NPMScan	Next Devtools MCP
Category	Developer Tools	Developer Tools
Quality signal	48/100 · Fair	86/100 · Excellent
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	No auth required	No auth required
Pricing	Free	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Verified
GitHub stars	0	828
Directory activity	0 views 0 installs 0 upvotes	8 views 0 installs 1 upvotes
Tools	23	4
Full listing	View NPMScan	View Next Devtools MCP

Tools & capabilities

NPMScan tools 23

search_packagesSearch the npm registry by name or keywords. Each result includes weekly/monthly download counts, dependent-package counts, and rank among npmscan's own top-100k-by-downloads snapshot, so you can tell an established package from an abandoned or squatted one that merely matches the query text — flag…
get_packageLatest version, install scripts (`preinstall`/`install`/`postinstall`/`prepare`), maintainers, license, recent version history, weekly downloads, GitHub stars, TypeScript support, days since last publish, ecosystem-wide download rank, a 3-month download trend, and an `isLatestVersionVulnerable`/`hi…
get_package_versionMetadata for one exact version plus an OSV.dev check scoped to that version — `isVulnerable`/`highestSeverity` as a direct safe/not-safe answer, with each finding's severity, summary, fixed version and `isMalware`. For checking a version pinned in a lockfile. A version npm has removed but OSV still…
get_maintainer_profilePackages an npm username currently maintains via npm's own `maintainer:<username>` search index, plus precomputed download/dependent totals across all of them. Lists the most-downloaded `limit` packages (default 50, max 250); totals still cover every package found. A plain info lookup, not a securi…
query_vulnerabilitiesOSV.dev lookup for known vulnerabilities affecting a package, optionally scoped to a version, with `isVulnerable`/`highestSeverity` as a direct verdict and each finding's severity, summary, fixed version and `isMalware`. For npm it also cross-checks the name/version against the registry: a name or…
batch_query_vulnerabilitiesOSV.dev lookup across a whole dependency inventory at once — pass a flat `packages` list, or paste raw `package.json`/lockfile/CycloneDX JSON/SPDX JSON content via `content` and it parses that for you. Chunks large inventories internally, with severity, summary, CVE aliases, fixed version and `isMa…
get_latest_advisoriesRecently published npm advisories from one of three sources (one per call): `type: "reviewed"` (default) is GitHub's curated, mostly CVE-backed set, filterable by severity, vulnerability category, affected package name, or an exact GHSA/CVE ID; `type: "malware"` is GitHub's own malicious-package ad…
get_cveNIST NVD lookup for one exact CVE ID (authoritative CVSS score/vector, CWEs, references), or a keyword/severity/CWE/date-range search. Enriched with CISA KEV status (actively exploited in the wild?) and FIRST.org EPSS (30-day exploitation probability). Falls back to the raw MITRE CVE record when NV…
analyze_install_scriptFetches a package's published tarball and statically scans its `preinstall`/`install`/`postinstall`/`prepare` lifecycle scripts — and the files they reference, pulled from the tarball itself — against npmscan's red-flags rubric (`child_process` use, network calls, sensitive-path/env access, obfusca…
analyze_transitive_dependenciesRecursively resolves 1-15 direct/root packages' dependency graphs to a configurable depth (default 2, max 3) and batch-checks every resolved package against OSV.dev — surfaces vulnerabilities buried several levels deep that a flat `batch_query_vulnerabilities` call would miss, with `vulnerablePaths…
check_package_provenanceChecks a version's npm/Sigstore publish provenance against reality: flags a non-GitHub-hosted builder or an attested source repo that doesn't match `package.json`'s own `repository` field; flags a package missing provenance while its npm-scope/maintainer peers consistently have it (skipped for vers…
check_maintainer_changesReconstructs a package's maintainer-add/remove history from the npm packument and flags account-takeover patterns — a new maintainer who published shortly after being added, a sudden full maintainer-list replacement, a long-standing maintainer quietly dropped, or a maintainer change not yet tied to…
+11 more on the listing page

Next Devtools MCP tools 4

nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.
nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).
nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

NPMScan

No confirmed install command for NPMScan yet — follow the setup steps linked from its listing page rather than a guessed package name.

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

NPMScan vs Next Devtools MCP

Which MCP server should you choose?

N
Choose NPMScan when

Choose Next Devtools MCP when

Feature & specification comparison

Tools & capabilities

NPMScan tools 23

Next Devtools MCP tools 4

Ready-to-paste client configs

NPMScan

Next Devtools MCP

Frequently asked questions

NChoose NPMScan when

Choose Next Devtools MCP when

NPMScan tools 23

Next Devtools MCP tools 4

NPMScan

Next Devtools MCP

Frequently asked questions

What is the main functional difference between NPMScan and Next Devtools MCP?

How do I install NPMScan or Next Devtools MCP in Claude Desktop, Cursor, or Windsurf?

Are NPMScan and Next Devtools MCP free to use, or do they require API keys?

Can I run both NPMScan and Next Devtools MCP at the same time in my AI client?

Which MCP server has higher directory engagement and quality ratings?

Popular comparisons with NPMScan

Popular comparisons with Next Devtools MCP

N
Choose NPMScan when