# NPMScan (remote · npmscan.com)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `npmscan.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/salemalem-npmscan/api-mcp.md), [page](https://verifymcp.io/servers/salemalem-npmscan/api-mcp)

## Channel facts

- Endpoint: `https://npmscan.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 505 tokens (~84/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 71, +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.

### 2026-08-02 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-01 (score 70)

First indexed and scored.

## MCP tools (6)

### `search_packages` (~72 tokens)

Search npm packages

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

Input parameters:

- `limit` (integer): Max results to return (default 20, max 50)
- `query` (string, required): Search text, e.g. a package name or keywords

### `get_package` (~77 tokens)

Get npm package details

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 parameters:

- `name` (string, required): Exact npm package name, e.g. "lodash" or "@scope/name"

### `get_package_version` (~76 tokens)

Get a specific npm 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 release.

Input parameters:

- `name` (string, required): Exact npm package name
- `version` (string, required): Exact version string, e.g. "4.17.21"

### `query_vulnerabilities` (~73 tokens)

Query known vulnerabilities for a package

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

Input parameters:

- `ecosystem` (string): OSV ecosystem, default "npm"
- `name` (string, required): npm package name
- `version` (string): Optional exact version to narrow results

### `batch_query_vulnerabilities` (~56 tokens)

Batch query known vulnerabilities

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 parameters:

- `packages` (array, required): 1-100 packages to check

### `get_latest_advisories` (~59 tokens)

Get latest npm security advisories

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

Input parameters:

- `page` (integer): Page number (default 1)
- `severity` (string): Filter by severity (default all)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/salemalem-npmscan/api-mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70

## Links

- Remote endpoint: https://npmscan.com/api/mcp
- Repository: https://github.com/salemalem/npmscan
- Changelog RSS feed: https://verifymcp.io/servers/salemalem-npmscan/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/salemalem-npmscan/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/salemalem-npmscan/api-mcp