# UNPKG (remote · mcp.unpkg.com)

Live npm and UNPKG data for AI agents: resolution, audits, import maps, malware/CVE checks.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://mcp.unpkg.com/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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1911 tokens (~119/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
  - Structured output schemas are declared (64% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the UNPKG MCP server?

UNPKG is a hosted endpoint at https://mcp.unpkg.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http unpkg-unpkg-mcp 'https://mcp.unpkg.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "unpkg-unpkg-mcp": {
      "url": "https://mcp.unpkg.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "unpkg-unpkg-mcp": {
      "type": "http",
      "url": "https://mcp.unpkg.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.unpkg-unpkg-mcp]
url = "https://mcp.unpkg.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add unpkg-unpkg-mcp --url 'https://mcp.unpkg.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  unpkg-unpkg-mcp:
    url: "https://mcp.unpkg.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "unpkg-unpkg-mcp": {
      "Transport": "http",
      "Url": "https://mcp.unpkg.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add unpkg-unpkg-mcp -t streamable-http -u 'https://mcp.unpkg.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "unpkg-unpkg-mcp": {
      "type": "http",
      "url": "https://mcp.unpkg.com/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-11-20 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 75, +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-11-08 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 74)

First indexed and scored.

## MCP tools (14)

### `resolve_package` (~87 tokens)

Resolve an npm package version

Resolve a package name plus exact version, dist-tag, or semver range to the version that exists on npm today, with its browser entry points. Use this instead of recalling versions from memory.

Input parameters:

- `package` (string, required): npm package name, e.g. react or @scope/name
- `version` (string): Exact version, dist-tag, or semver range. Defaults to latest.

Output parameters:

- `distTags` (object)
- `entryPoints` (object)
- `name` (string)
- `peerDependencies` (object)
- `requested` (string)
- `resolvedVersion` (string)

### `list_files` (~99 tokens)

List files in a package version

List the real files inside an exact or resolvable package version via UNPKG ?meta. Use this before choosing a file path; never guess paths.

Input parameters:

- `limit` (integer): Max files to return. Defaults to 200.
- `package` (string, required)
- `path` (string): Directory prefix inside the package, e.g. /dist/. Defaults to /.
- `version` (string): Defaults to latest; resolved before listing.

Output parameters:

- `files` (array)
- `package` (string)
- `prefix` (string)
- `totalFiles` (number)
- `truncated` (boolean)
- `version` (string)

### `build_file_url` (~163 tokens)

Build a canonical UNPKG file URL

Build a direct UNPKG file URL (the original file lookup) with a deliberate version policy, verifying the file exists when a path is given.

Input parameters:

- `file` (string): File path inside the package. Defaults to the resolved entry point.
- `package` (string, required)
- `policy` (string): preserve: keep the given spec (default). exact: resolved version. patch: major.minor (bug fixes flow). range: ^major.minor.patch.
- `subpath` (string): Package subpath import, e.g. hooks for preact/hooks. Resolved through the exports map, then file discovery. Ignored when file is given.
- `version` (string): Exact version, dist-tag, or range to resolve. Defaults to latest.

Output parameters:

- `file` (string)
- `package` (string)
- `resolvedVersion` (string)
- `specUsed` (string)
- `url` (string)
- `verifiedFileExists` (boolean|null)

### `audit_dependencies` (~314 tokens)

Audit dependencies for UNPKG conversion

Classify a project's runtime dependencies for conversion to direct UNPKG file lookups, in framework context when given. Read the project's package.json yourself and pass its dependencies map; this tool checks each package against live npm/UNPKG data and returns convert_now / convert_carefully / keep_bundled / needs_review with suggested URLs and an import map for the safe conversions. IMPORTANT: suitability is not usage. Before calling, scan the project's HTML/files for an existing import map and CDN URLs and pass them as existingImports; entries already on UNPKG come back as already_on_unpkg, not conversion candidates. If you did not scan, say so — currentUsage will be absent rather than falsely 'not detected'. Only pass runtime dependencies, never devDependencies.

Input parameters:

- `dependencies` (object, required): Map of package name to the version spec from package.json, e.g. { "preact": "^10.25.4" }
- `existingImports` (object): Existing imports found in the project: bare specifier to current URL, typically an import map extracted from HTML (include subpath keys like preact/hooks). Pass {} if you scanned and found none. Omit…
- `framework` (string): The project's framework, if any. Framework-managed packages (react/react-dom in Next, vue in Nuxt, ...) are classified keep_bundled in context. Auto-detected from the dependency map when omitted.

Output parameters:

- `currentStateSummary` (object)
- `dependencies` (array)
- `framework` (string|null)
- `frameworkNote` (string|null)
- `impact` (object)
- `importmap` (object)
- `importmapScope` (string)
- `mapValidation`
- `nextSteps` (string)
- `peerImportsAdded` (array)
- `peerNotes` (array)
- `scopeNote` (string)
- `shieldNote` (string|null)
- `shieldVerdicts`
- `summary` (object)

### `verify_url` (~48 tokens)

Verify a UNPKG URL resolves

Check that a UNPKG file URL actually resolves (follows redirects) before you put it in a project.

Input parameters:

- `url` (string, required): A full https://unpkg.com/... file URL.

Output parameters:

- `contentType` (string|null)
- `finalUrl` (string)
- `ok` (boolean)
- `status` (number)

### `generate_importmap` (~48 tokens)

Generate an import map for UNPKG packages

Resolve a set of bare specifiers to UNPKG file URLs and return a ready-to-paste import map. Entry files are resolved live from each package.

Input parameters:

- `entries` (array, required)

Output parameters:

- `importmap` (object)
- `resolved` (object)

### `check_importmap` (~103 tokens)

Validate an import map as a system

Validate an existing or proposed import map: every UNPKG URL resolves, files exist, versions are mutually consistent (including react/react-dom pairing and duplicate-version skew), loose specs are flagged, and framework-managed packages are errors when a framework is given or detected. Run this after generate_importmap or an audit, before committing to a conversion.

Input parameters:

- `framework` (string)
- `imports` (object, required): The import map's imports object: bare specifier to URL.

Output parameters:

- `entries` (array)
- `framework` (string|null)
- `globalIssues` (array)
- `ok` (boolean)

### `search_packages` (~132 tokens)

Search npm for browser-suitable packages

Search npm for a need (e.g. 'date picker', 'markdown parser') and annotate each result with browser readiness for direct UNPKG file lookup: browser-ready ESM, CommonJS-only, or unclear, with the entry file and size when known. Ranking is npm's relevance order; readiness is annotated, never hidden, so a CJS-only result is visible as such rather than silently dropped.

Input parameters:

- `limit` (integer): Results to annotate. Defaults to 5.
- `query` (string, required): What the package should do, e.g. 'confetti', 'sanitize html', 'date picker'.

Output parameters:

- `note` (string)
- `query` (string)
- `results` (array)

### `estimate_migration_impact` (~169 tokens)

Rough bandwidth/cost impact of a conversion

Order-of-magnitude estimate of bandwidth offloaded (and hosting dollars, if a $/GB is given) when bytes move from first-party hosting to UNPKG. Range-based with explicit assumptions and caveats; it cannot forecast latency or Core Web Vitals. Get unpkgBytesPerPageLoad from audit_dependencies' impact.convertNowEntryBytes plus any transitive files the caller chooses to include.

Input parameters:

- `bandwidthCostPerGbUsd` (number): Current hosting $/GB, if known. Omit to skip dollars.
- `browserCacheRate` (number): Share of loads served from browser cache. Default 0.5.
- `monthlyPageViews` (number, required)
- `unpkgBytesPerPageLoad` (number, required): Raw bytes per page load moving to UNPKG.

Output parameters:

- `assumptions` (array)
- `betterMetrics` (array)
- `caveats` (array)
- `monthlyGbOffloaded` (object)
- `monthlySavingsUsd`
- `perLoadWireBytes`
- `transferTimeEquivalentMs` (object)

### `shield_whoami` (~45 tokens)

Shield account for the logged-in user

Return the Shield account, organization, and entitlements for the OAuth login on this connection. Requires an approved Shield account; anonymous connections get an authorization_required error with reconnect instructions.

### `shield_simulate_request` (~87 tokens)

Simulate a Shield edge decision

Preview what Shield would do for one package@version request (optionally with referer/origin) under the logged-in user's effective pin/block rules, using the same rule-matching semantics as the edge.

Input parameters:

- `origin` (string)
- `package` (string, required)
- `path` (string)
- `referer` (string)
- `version` (string, required)

### `shield_check_packages` (~86 tokens)

Malware verdicts and CVEs for package versions

Check exact package@version pairs against Shield intel: malware verdict (with review state) and CVEs affecting that version, including the first patched version. Works anonymously for packages you name (25 per call); Shield login raises the cap to 200. Domain data still requires login. Missing pairs were not scanned yet — absence is not a clean verdict.

Input parameters:

- `packages` (array, required)

### `shield_domain_packages` (~127 tokens)

Shield-observed packages on your domains

List the caller's verified domains with package counts, or the packages Shield has observed on one domain. With includeThreats, one domain's packages come back annotated with malware verdicts and CVEs, ranked by the domain's own traffic. Requires Shield login.

Input parameters:

- `days` (integer): Lookback window for threats mode. Default 30; 0 = all-time.
- `domain` (string): One verified domain. Omit to list domains with package counts.
- `includeThreats` (boolean): Annotate one domain's packages with verdicts and CVEs. Requires domain.

### `shield_watchlist_status` (~36 tokens)

Your Shield watchlist, pins, and blocks

Return the logged-in org's monitored packages, blocklist entries, and pin policies as Shield currently holds them. Requires Shield login.

## Diagnostics

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

## Score history

- 2026-11-21: 80
- 2026-11-20: 80
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75
- 2026-11-09: 75
- 2026-11-08: 74
- 2026-11-07: 74

## Common questions

### What is the UNPKG MCP server?

UNPKG is an MCP server listed in the public MCP registry as io.github.unpkg/unpkg-mcp. Live npm and UNPKG data for AI agents: resolution, audits, import maps, malware/CVE checks. This page covers its hosted endpoint (https://mcp.unpkg.com/mcp).

### Is the UNPKG MCP server safe to use?

UNPKG scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the UNPKG MCP server expose?

UNPKG exposes 14 tools: resolve_package, list_files, build_file_url, audit_dependencies, verify_url, and 9 more. Their descriptions and schemas cost roughly 1,544 tokens of context every time the server is loaded.

### Does the UNPKG MCP server require authentication?

No. We connected to UNPKG without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UNPKG MCP server still maintained?

UNPKG is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the UNPKG MCP server?

VerifyMCP ran 13 checks on UNPKG, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.unpkg.com/mcp
- Repository: https://github.com/unpkg/unpkg-mcp
- Website: https://mcp.unpkg.com/
- Changelog RSS feed: https://verifymcp.io/servers/unpkg-unpkg-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/unpkg-unpkg-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/unpkg-unpkg-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/unpkg-unpkg-mcp/mcp
