Jsdelivr
NPM · @PIPEWORX/MCP-JSDELIVR · 2 COMPONENTS
JSDelivr Data API MCP
Available components
Last scanned (2 hours ago)
Scores higher than 58% of npm servers
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jsdelivr). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 454 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 −4
- Provenance: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 80
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-jsdelivr@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-jsdelivr |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-jsdelivr/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649506550 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2e625aa5a79529237de76d6b7d99395cc305187bce423bdb511711a67b99aa20324e321a0d2a68262e1c4f4e9c5b45cf784280bdc152cda2adda9af8f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
gh_repo_stats ~61
Return JSDelivr CDN request count and bandwidth for files served from a GitHub owner/repo for the specified period (day/week/month/quarter/year).
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| period | string | – | – |
| repo | string | yes | – |
No output schema declared.
No examples provided.
list_npm_files ~150
jsDelivr Data API — the file tree of one published npm package version (latest by default) as jsDelivr indexes it for CDN delivery. Returns the directory structure with each file's path, byte size, content hash and type, read from jsDelivr's package index. Answers which files, entry points and build outputs an npm package version actually ships.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | – |
| version | string | – | Specific published version, e.g. "4.17.21". Omit this argument entirely to get the latest published version — do not pass the literal string "latest"; jsDelivr's API rejects that as an unresolvable v… |
No output schema declared.
No examples provided.
list_npm_versions ~26
All published versions for an npm package.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | – |
No output schema declared.
No examples provided.
npm_package_stats ~66
Request counts + bandwidth for an npm package served via JSDelivr.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | npm package name (scoped allowed) |
| period | string | – | day | week | month | quarter | year | s-month | s-quarter | s-year (default month) |
No output schema declared.
No examples provided.
resolve_version ~43
Resolve a semver range or tag to a concrete published version.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | – |
| range | string | – | Semver range (default "latest") |
No output schema declared.
No examples provided.
top_npm_packages ~56
JSDelivr leaderboard of top-served npm packages.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | hits (default) | bandwidth |
| limit | number | – | 1-100 (default 25) |
| period | string | – | – |
No output schema declared.
No examples provided.
How do I install the Jsdelivr MCP server?
Jsdelivr runs locally as an npm package, launched with npx -y @pipeworx/mcp-jsdelivr. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-jsdelivr
claude mcp add pipeworx-io-jsdelivr -- npx -y @pipeworx/mcp-jsdelivr
What is the Jsdelivr MCP server?
Jsdelivr is an MCP server listed in the public MCP registry as io.github.pipeworx-io/jsdelivr. JSDelivr Data API MCP. This page covers its npm package (@pipeworx/mcp-jsdelivr).
Is the Jsdelivr MCP server safe to use?
Jsdelivr scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Jsdelivr MCP server expose?
Jsdelivr exposes 6 tools: npm_package_stats, gh_repo_stats, top_npm_packages, list_npm_files, resolve_version, list_npm_versions. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Is the Jsdelivr MCP server still maintained?
Jsdelivr is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Jsdelivr MCP server under?
Jsdelivr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.