io.github.unpkg/unpkg-mcp · v1.0.0 · developer-tools
UNPKG is healthy: it completed an MCP handshake in 677 ms and exposes 14 tools.
Live npm and UNPKG data for AI agents: resolution, audits, import maps, malware/CVE checks.
Endpoint: https://mcp.unpkg.com/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 14 |
| Latency | 677 ms |
| Last checked (UTC) | 2026-11-07T09:35:23.254Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-07T09:35:23.254Z | Healthy | 677 |
resolve_package | 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. |
list_files | List the real files inside an exact or resolvable package version via UNPKG ?meta. Use this before choosing a file path; never guess paths. |
build_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. |
audit_dependencies | 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 |
verify_url | Check that a UNPKG file URL actually resolves (follows redirects) before you put it in a project. |
generate_importmap | 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. |
check_importmap | 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 afte |
search_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, s |
estimate_migration_impact | 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. |
shield_whoami | 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 | 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. |
shield_check_packages | 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 |
shield_domain_packages | 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. |
shield_watchlist_status | Return the logged-in org's monitored packages, blocklist entries, and pin policies as Shield currently holds them. Requires Shield login. |