npmscan

Security analysis for npm packages, built for AI agents and developer tools.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Search Packages: Search the npm registry by name or keywords. Returns matching packages with a link to their full npmscan.com risk/analysis page.
  • Get Package: Fetch npm registry metadata for a package: latest version, install scripts (preinstall/postinstall are a key risk signal), maintainers, license, and recent version history. Includes a lin
  • Get Package Version: Fetch registry metadata for one exact version of a package (dependencies, install scripts, tarball). Use this to check a version pinned in a lockfile rather than the latest releas

What data it sees

Do you need an account

No: the server works without sign-in

Security analysis for npm packages, built for AI agents and developer tools.

NPMScan helps agents inspect npm packages before installation by checking for:

  • Suspicious install scripts
  • Obfuscated or potentially malicious code
  • Credential and environment-variable access
  • Network and data-exfiltration indicators
  • Known vulnerabilities
  • Maintainer and ownership changes
  • Risky package updates and version differences

Use this MCP server to investigate package risk, compare versions, and make safer dependency decisions directly from an MCP-compatible client.

No account or API key is required.

Website: https://npmscan.com

How to connect

How to connect npmscan to Claude

The server address to paste into Claude settings:

https://npmscan--shyngys-shynbolatov.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect npmscan to ChatGPT

The server address to paste into ChatGPT settings:

https://npmscan--shyngys-shynbolatov.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect npmscan to Cursor

The server address to paste into Cursor settings:

https://npmscan--shyngys-shynbolatov.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (6)

Raw names from tools/list. Only developers need these.

search_packagesSearch the npm registry by name or keywords. Returns matching packages with a link to their full npmscan.com risk/analysis page.
get_packageFetch npm registry metadata for a package: latest version, install scripts (preinstall/postinstall are a key risk signal), maintainers, license, and recent version history. Includes a link to the full npmscan.com analysis page.
get_package_versionFetch registry metadata for one exact version of a package (dependencies, install scripts, tarball). Use this to check a version pinned in a lockfile rather than the latest release.
query_vulnerabilitiesQuery OSV.dev for known vulnerabilities affecting an npm package, optionally scoped to one version. Use before recommending or installing a package.
batch_query_vulnerabilitiesQuery OSV.dev for known vulnerabilities across up to 100 npm packages at once — ideal for scanning a whole package.json/lockfile in one call.
get_latest_advisoriesBrowse the most recently published, reviewed GitHub Security Advisories for the npm ecosystem, optionally filtered by severity.