NPMScan

REMOTE · NPMSCAN.COM · SCANNED AUG 3

Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups

Available components

71 71 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security74

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 505 tokens (~84/item across 6 items; 6 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management7

Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · npmscan.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http salemalem-npmscan https://npmscan.com/api/mcp

# ~/.codex/config.toml

[mcp_servers.salemalem-npmscan]
url = "https://npmscan.com/api/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "salemalem-npmscan": {
      "type": "remote",
      "url": "https://npmscan.com/api/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add salemalem-npmscan --url https://npmscan.com/api/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  salemalem-npmscan:
    url: "https://npmscan.com/api/mcp"

// mcp.json

{
  "mcpServers": {
    "salemalem-npmscan": {
      "type": "http",
      "url": "https://npmscan.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
1 Aug 26 70

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://npmscan.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=npmscan.com	CN=YE1,O=Let's Encrypt,C=US	29 Jul 2026	27 Oct 2026	ECDSA 256	ECDSA-SHA384	52d75574f4a14a2bea5936c4ae214956a24
SANs: npmscan.com
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of npmscan.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
npmscan.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	origin-when-cross-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://npmscan.com/api/mcp	Verified	200
http (plaintext)	http://npmscan.com/api/mcp	HTTPS enforced	301	https://npmscan.com/api/mcp

MCP tools — 6 exposed · ~413 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

batch_query_vulnerabilities Batch query known vulnerabilities ~56

Query OSV.dev for known vulnerabilities across up to 100 npm packages at once — ideal for scanning a whole package.json/lockfile in one call.

Input Output Examples

Name	Type	Req	Description
packages	array	yes	1-100 packages to check

No output schema declared.

No examples provided.

get_latest_advisories Get latest npm security advisories ~59

Browse the most recently published, reviewed GitHub Security Advisories for the npm ecosystem, optionally filtered by severity.

Input Output Examples

Name	Type	Req	Description
page	integer	—	Page number (default 1)
severity	string	—	Filter by severity (default all)

No output schema declared.

No examples provided.

get_package Get npm package details ~77

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 link to the full npmscan.com analysis page.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Exact npm package name, e.g. "lodash" or "@scope/name"

No output schema declared.

No examples provided.

get_package_version Get a specific npm package version ~76

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 release.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Exact npm package name
version	string	yes	Exact version string, e.g. "4.17.21"

No output schema declared.

No examples provided.

query_vulnerabilities Query known vulnerabilities for a package ~73

Query OSV.dev for known vulnerabilities affecting an npm package, optionally scoped to one version. Use before recommending or installing a package.

Input Output Examples

Name	Type	Req	Description
ecosystem	string	—	OSV ecosystem, default "npm"
name	string	yes	npm package name
version	string	—	Optional exact version to narrow results

No output schema declared.

No examples provided.

search_packages Search npm packages ~72

Search the npm registry by name or keywords. Returns matching packages with a link to their full npmscan.com risk/analysis page.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max results to return (default 20, max 50)
query	string	yes	Search text, e.g. a package name or keywords

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

1 Aug 3 Aug