io.github.mrfentmen/unpkg-mcp vs Npm
io.github.mrfentmen/unpkg-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). Npm is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.mrfentmen/unpkg-mcp |  Npm |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (npm): 234 Downloads/week (npm): 56 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.mrfentmen/unpkg-mcp | Npm |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-08 (better) | 2026-11-03 (worse) |
| Where it runs (differs) | On your machine (unpkg-mcp) | Remote server (gateway.pipeworx.io/npm/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mrfentmen/awesome-servers | github.com/pipeworx-io/mcp-npm |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.mrfentmen/unpkg-mcp
Package file metadata from the unpkg CDN. No key required.
Npm
npm MCP — wraps the npm Registry API (free, no auth)
How to run each
io.github.mrfentmen/unpkg-mcp As a local MCP server: npm package
claude mcp add --transport stdio unpkg-mcp -- npx -y unpkg-mcpNpm As a remote MCP server
claude mcp add --transport http npm https://gateway.pipeworx.io/npm/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Npm has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.mrfentmen/unpkg-mcp publish no settings it asks for, so we do not compare settings.
What it can do: io.github.mrfentmen/unpkg-mcp · What it can do: Npm · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.