mcpcost

io.github.mrfentmen/jsdelivr-mcp

jsdelivr-mcp

Is the io.github.mrfentmen/jsdelivr-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-09.

Package versions and CDN statistics from jsDelivr. No key required.

alive probed 2026-11-15 · unchanged since 2026-11-09

5tools
751tokens in Claude
0.4 %of Claude's 200k window
0.3×the median server
354 msto initialize
10 msto list tools
Run it
npx -y @mrfentmen/jsdelivr-mcp@1.0.3 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
jsdelivr-mcp 1.0.0
Capabilities
tools
Instructions
none
Of a 1M window
<0.1 % of a 1M context window
Count
751 tokens in Claude, exact, measured 2026-11-09. With the Claude Code prefix mcp__…__ on each tool name: 826. The o200k_base estimate is 427. Counted again when the tool definitions change. Method.
Repository
https://github.com/mrfentmen/awesome-servers
Registry
active, updated 2026-11-08 · registry entry
Changes
3 recorded, reachable in 3 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.76×.

Tool≈ Claude tokenso200k estimateShare of this server
resolve_version18510525 %
version_detail18310424 %
version_list1649322 %
stats1116315 %
package1096215 %

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention jsdelivr or statistics or required.

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-11-09 08:46alive175 ms5751427
2026-10-25 06:55alive342 ms2232125
2026-10-18 06:41alive354 ms2125

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher