Developer Tools
unpkg.com
MCP server that resolves npm package versions and UNPKG file paths, audits dependencies, and verifies file URLs for developers.
ENDPOINT 1
https://mcp.unpkg.com/mcp
MCP server metadata
- Name
- unpkg-mcp
- Version
- 1.0.0
Live npm and UNPKG data for direct file lookups (https://unpkg.com/<package>@<version>/<file>) — the original UNPKG file serving. Do not suggest esm.unpkg.com by default: it is a beta transform service, appropriate only when a package has no browser-ready file and the user opts in. Use resolve_package/list_files instead of guessing versions or paths, build_file_url for canonical URLs, Before an audit, scan the project's HTML for existing import maps and CDN URLs (unpkg.com, cdn.jsdelivr.net, esm.sh, plain script tags) and pass them as existingImports — suitability is not usage, and a project may already be converted. Lead audit summaries with current state. shield_check_packages works anonymously for package@versions the user names (malware verdicts and CVEs); only domain, watchlist, and simulation tools need Shield login. If a shield_* tool returns authorization_required, walk the user through connecting: MCP server must be https://mcp.unpkg.com/mcp, then Authenticate from the client's MCP server panel, sign in at shield.unpkg.com in the browser, Approve, retry. Never present the oauth-protected-resource URL as something the user should open. audit_dependencies and check_importmap before converting a project, and estimate_migration_impact for rough bandwidth ranges (never exact savings promises). Recommend against UNPKG when a bundler or framework already owns the dependency. Framework apps (Next, Nuxt, ...) keep framework-managed packages bundled; only standalone browser surfaces convert. Read the conversion playbook resource before a project audit.
Known tools 14
resolve_packageResolve a package name plus exact version, dist-tag, or semver range to the version that exists on npm today, with its browser entry points.
Inferred read-onlylist_filesList the real files inside an exact or resolvable package version via UNPKG ?
Inferred read-onlybuild_file_urlBuild a direct UNPKG file URL (the original file lookup) with a deliberate version policy, verifying the file exists when a path is given.
Inferred read-onlyaudit_dependenciesClassify a project's runtime dependencies for conversion to direct UNPKG file lookups, in framework context when given.
Inferred read-onlyverify_urlCheck that a UNPKG file URL actually resolves (follows redirects) before you put it in a project.
Inferred read-onlygenerate_importmapResolve a set of bare specifiers to UNPKG file URLs and return a ready-to-paste import map.
Inferred read-onlycheck_importmapValidate 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.
Inferred read-onlyestimate_migration_impactOrder-of-magnitude estimate of bandwidth offloaded (and hosting dollars, if a $/GB is given) when bytes move from first-party hosting to UNPKG.
Inferred read-onlyshield_whoamiReturn the Shield account, organization, and entitlements for the OAuth login on this connection.
Inferred read-onlyshield_simulate_requestPreview 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.
Inferred read-onlyshield_check_packagesCheck exact package@version pairs against Shield intel: malware verdict (with review state) and CVEs affecting that version, including the first patched version.
Inferred read-onlyshield_domain_packagesList the caller's verified domains with package counts, or the packages Shield has observed on one domain.
Inferred read-onlyshield_watchlist_statusReturn the logged-in org's monitored packages, blocklist entries, and pin policies as Shield currently holds them.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.unpkg-mcp]
url = "https://mcp.unpkg.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"unpkg-mcp": {
"type": "http",
"url": "https://mcp.unpkg.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: unpkg-mcp
Remote MCP URL: https://mcp.unpkg.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"unpkg-mcp": {
"url": "https://mcp.unpkg.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"unpkg-mcp": {
"type": "http",
"url": "https://mcp.unpkg.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "unpkg-mcp",
"transport": "streamable-http",
"url": "https://mcp.unpkg.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for unpkg.com was fetched 2026-11-07T21:27:23.135Z.
unpkg.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.