NPMScan vs Magic MCP
A side-by-side look at the NPMScan and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NPMScanDeveloper ToolsDetect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups48FairAuth: no auth requiredVerdict: choose NPMScan for developer tools work; choose Magic MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
NChoose NPMScan when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You want tools like
search_packages, get_package, get_package_version.
Choose Magic MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NPMScan | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 48/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Paid service |
| Required env vars | None listed | TWENTY_FIRST_API_KEY |
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…
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.
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
Frequently asked questions
NPMScan is categorized under Developer Tools and uses an install path we have not confirmed yet. Magic MCP belongs to Developer Tools and uses a local stdio subprocess. Pick NPMScan for developer tools work and Magic MCP for developer tools.
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.
NPMScan is listed as free. Auth: no auth required. Magic MCP is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add npmscan-2 and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NPMScan has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 5,997 GitHub stars.
