OpenZeppelin Stylus Contracts vs ipfs-setup
ipfs-setup is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
OpenZeppelin Stylus Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). ipfs-setup is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-24. 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 |  OpenZeppelin Stylus Contracts | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace barnburner121/claude-plugin-marketplace | Not listed | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | OpenZeppelin Stylus Contracts | ipfs-setupno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/stylus/mcp) | On your machine (@barnburner121/plugin-hub-mcp) |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/barnburner121/claude-plugin-marketplace |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
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.
-
mcp-server com.puter/mcp-server
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
What each says it does
OpenZeppelin Stylus Contracts
Access to OpenZeppelin Stylus Contracts.
ipfs-setup
Generate IPFS integration for decentralized storage
How to run each
OpenZeppelin Stylus Contracts As a remote MCP server
claude mcp add --transport http openzeppelin-stylus https://mcp.openzeppelin.com/contracts/stylus/mcpipfs-setup
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only OpenZeppelin Stylus Contracts has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of ipfs-setup publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: OpenZeppelin Stylus Contracts · What it can do: ipfs-setup · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.