Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

UNPKG

REMOTE · MCP.UNPKG.COM

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

Available components

+3 this week 80 Trust /100

Last scanned (16 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security80
  • 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. 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
  • Structured output schemas are declared (64% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 9 Nov 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.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 74

    First indexed and scored.

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 21 Nov 2026 · Probed https://mcp.unpkg.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=unpkg.com CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 c7052c40a23e38ab139fd35723681c4f
SANs: unpkg.com, mcp.unpkg.com, *.mcp.unpkg.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.unpkg.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
unpkg.com. No DS 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
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
www-authenticate Bearer resource_metadata="https://mcp.unpkg.com/.well-known/oauth-protected-resource", scope="shield:read shield:simulate"

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.unpkg.com/mcp Verified 200
http (plaintext) http://mcp.unpkg.com/mcp HTTPS enforced 301 https://mcp.unpkg.com/mcp
MCP tools · 14 exposed · ~1,544 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audit_dependencies ~314

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.

NameTypeReqDescription
dependenciesobjectyesMap of package name to the version spec from package.json, e.g. { "preact": "^10.25.4" }
existingImportsobject–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…
frameworkstring–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.
NameTypeReqDescription
currentStateSummaryobjectyes–
dependenciesarrayyes–
frameworkstring|nullyes–
frameworkNotestring|nullyes–
impactobjectyes–
importmapobjectyes–
importmapScopestringyes–
mapValidation–yes–
nextStepsstringyes–
peerImportsAddedarrayyes–
peerNotesarrayyes–
scopeNotestringyes–
shieldNotestring|nullyes–
shieldVerdicts–yes–
summaryobjectyes–

No examples provided.

build_file_url ~163

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

NameTypeReqDescription
filestring–File path inside the package. Defaults to the resolved entry point.
packagestringyes–
policystring–preserve: keep the given spec (default). exact: resolved version. patch: major.minor (bug fixes flow). range: ^major.minor.patch.
subpathstring–Package subpath import, e.g. hooks for preact/hooks. Resolved through the exports map, then file discovery. Ignored when file is given.
versionstring–Exact version, dist-tag, or range to resolve. Defaults to latest.
NameTypeReqDescription
filestringyes–
packagestringyes–
resolvedVersionstringyes–
specUsedstringyes–
urlstringyes–
verifiedFileExistsboolean|nullyes–

No examples provided.

check_importmap ~103

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.

NameTypeReqDescription
frameworkstring––
importsobjectyesThe import map's imports object: bare specifier to URL.
NameTypeReqDescription
entriesarrayyes–
frameworkstring|nullyes–
globalIssuesarrayyes–
okbooleanyes–

No examples provided.

estimate_migration_impact ~169

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.

NameTypeReqDescription
bandwidthCostPerGbUsdnumber–Current hosting $/GB, if known. Omit to skip dollars.
browserCacheRatenumber–Share of loads served from browser cache. Default 0.5.
monthlyPageViewsnumberyes–
unpkgBytesPerPageLoadnumberyesRaw bytes per page load moving to UNPKG.
NameTypeReqDescription
assumptionsarrayyes–
betterMetricsarrayyes–
caveatsarrayyes–
monthlyGbOffloadedobjectyes–
monthlySavingsUsd–yes–
perLoadWireBytes–yes–
transferTimeEquivalentMsobjectyes–

No examples provided.

generate_importmap ~48

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.

NameTypeReqDescription
entriesarrayyes–
NameTypeReqDescription
importmapobjectyes–
resolvedobjectyes–

No examples provided.

list_files ~99

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

NameTypeReqDescription
limitinteger–Max files to return. Defaults to 200.
packagestringyes–
pathstring–Directory prefix inside the package, e.g. /dist/. Defaults to /.
versionstring–Defaults to latest; resolved before listing.
NameTypeReqDescription
filesarrayyes–
packagestringyes–
prefixstringyes–
totalFilesnumberyes–
truncatedbooleanyes–
versionstringyes–

No examples provided.

resolve_package ~87

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.

NameTypeReqDescription
packagestringyesnpm package name, e.g. react or @scope/name
versionstring–Exact version, dist-tag, or semver range. Defaults to latest.
NameTypeReqDescription
distTagsobjectyes–
entryPointsobjectyes–
namestringyes–
peerDependenciesobjectyes–
requestedstringyes–
resolvedVersionstringyes–

No examples provided.

search_packages ~132

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.

NameTypeReqDescription
limitinteger–Results to annotate. Defaults to 5.
querystringyesWhat the package should do, e.g. 'confetti', 'sanitize html', 'date picker'.
NameTypeReqDescription
notestringyes–
querystringyes–
resultsarrayyes–

No examples provided.

shield_check_packages ~86

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.

NameTypeReqDescription
packagesarrayyes–

No output schema declared.

No examples provided.

shield_domain_packages ~127

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.

NameTypeReqDescription
daysinteger–Lookback window for threats mode. Default 30; 0 = all-time.
domainstring–One verified domain. Omit to list domains with package counts.
includeThreatsboolean–Annotate one domain's packages with verdicts and CVEs. Requires domain.

No output schema declared.

No examples provided.

shield_simulate_request ~87

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.

NameTypeReqDescription
originstring––
packagestringyes–
pathstring––
refererstring––
versionstringyes–

No output schema declared.

No examples provided.

shield_watchlist_status ~36

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shield_whoami ~45

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_url ~48

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

NameTypeReqDescription
urlstringyesA full https://unpkg.com/... file URL.
NameTypeReqDescription
contentTypestring|nullyes–
finalUrlstringyes–
okbooleanyes–
statusnumberyes–

No examples provided.

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.

remote · mcp.unpkg.com

# add to Claude Code
claude mcp add --transport http unpkg-unpkg-mcp 'https://mcp.unpkg.com/mcp'
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.