OpenZeppelin Solidity Contracts vs Automaton Onchain & URL Tools
OpenZeppelin Solidity Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Automaton Onchain & URL Tools is an MCP server published by automaton-tx-explainer.vercel.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  OpenZeppelin Solidity Contracts | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 No figure published 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 | Automaton Onchain & URL Tools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/solidity/mcp) | Remote server (automaton-tx-explainer.vercel.app/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 | Not stated | Not stated |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | Responded 35 h ago | Responded 40 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
OpenZeppelin Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
Automaton Onchain & URL Tools
Paid x402 tools: tx, approvals, address, contract risk (Base/ETH/BSC) + URL safety.
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/mcpAutomaton Onchain & URL Tools As a remote MCP server
claude mcp add --transport http base-tools https://automaton-tx-explainer.vercel.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Only OpenZeppelin Solidity Contracts has
solidity-accountsolidity-customsolidity-erc1155solidity-erc20solidity-erc721solidity-governorsolidity-rwasolidity-stablecoin
Only Automaton Onchain & URL Tools has
base_address_inspectbase_contract_riskbase_token_approvalsbase_tx_explainbsc_address_inspectbsc_contract_riskbsc_token_approvalsbsc_tx_explaincalldata_decodeens_resolveethereum_address_inspectethereum_contract_risk
Show the remaining 8
ethereum_token_approvalsethereum_tx_explaingas_snapshotpingtoken_reporturl_safety_checkwallet_portfoliowallet_report
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Automaton Onchain & URL Tools as of 2026-10-17). More tools is not better in itself: compare what each needs for the job.
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: Automaton Onchain & URL Tools · 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.