ipfs-setup vs com.puter/mcp-server
ipfs-setup is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
ipfs-setup is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. com.puter/mcp-server is an MCP server published by puter.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.puter/mcp-server | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 4 110 Stars (GitHub): 43 867 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 | ipfs-setupno longer listed · | com.puter/mcp-server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 43 867 |
| Forks (GitHub) (differs) | 0 | 4 110 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (mcp.puter.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/heyputer/puter |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ipfs-setup
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Pin files and websites to IPFS from Claude. x402 USDC payments on Base — no account needed.
-
ipfs-toolkit io.tkllabs.bh.mcp-servers/ipfs-toolkit
Store, retrieve, and pin encrypted files on IPFS via MCP tools for AI agents and workflows
-
pinata-mcp io.github.mrfentmen/pinata-mcp
MCP server for Pinata IPFS: pinned files, pin JSON, unpin. Needs a free API key.
-
Build real-time collaborative apps on Cloudflare Workers with DeepSpace SDK (forthcoming)
-
Use native Torii MCP on deployed Iroha networks such as Taira for live account, asset, contract, governance, and transaction workflows.
-
AI skills for building fullstack Aptos dApps — Move smart contracts, TypeScript SDK, wallet integration, security auditing, and gas optimization.
What each says it does
ipfs-setup
Generate IPFS integration for decentralized storage
com.puter/mcp-server
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
How to run each
ipfs-setup
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.puter/mcp-server As a remote MCP server
claude mcp add --transport http com-puter-mcp-server https://mcp.puter.com/Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.puter/mcp-server 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
Neither one's marketplaces publish the settings it asks for.
What it can do: ipfs-setup · What it can do: com.puter/mcp-server · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.