OpenZeppelin Solidity Contracts vs SwiftNodes RPC
OpenZeppelin Solidity Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). SwiftNodes RPC is an MCP server published by swiftnodes.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  SwiftNodes RPC | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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 | OpenZeppelin Solidity Contracts | SwiftNodes RPC |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/solidity/mcp) | Remote server (rpc.swiftnodes.io/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/swiftnodes/swiftnodes-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | Responded 17 h ago | not checked yet |
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
OpenZeppelin Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
SwiftNodes RPC
Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.
How to run each
OpenZeppelin Solidity Contracts As a remote MCP server
claude mcp add --transport http openzeppelin-solidity https://mcp.openzeppelin.com/contracts/solidity/mcpSwiftNodes RPC As a remote MCP server
claude mcp add --transport http swiftnodes https://rpc.swiftnodes.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only OpenZeppelin Solidity Contracts has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of SwiftNodes RPC 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 Solidity Contracts · What it can do: SwiftNodes RPC · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.