Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Solidity Contracts vs MCP Agentic Wallet — open-source session management for x402

OpenZeppelin Solidity Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). MCP Agentic Wallet — open-source session management for x402 is an MCP server published by MCPVOT. 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

Where each is published
MarketplaceOpenZeppelin Solidity ContractsMCP Agentic Wallet — open-source session management for x402
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

OpenZeppelin Solidity Contracts vs MCP Agentic Wallet — open-source session management for x402
FactOpenZeppelin Solidity ContractsMCP Agentic Wallet — open-source session management for x402
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/solidity/mcp)Not stated
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)8Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/mcpvot/mcp-agentic-wallet
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days agono remote endpoint we check

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

In its own words, on Docker MCP Catalog:

Access to OpenZeppelin Solidity Contracts.

MCP Agentic Wallet — open-source session management for x402

In its own words, on Official MCP Registry:

Open-source EIP-2612 Permit-based wallet sessions for AI agents using MCP.

How to run each

OpenZeppelin Solidity Contracts As a remote MCP server

Claude Code
claude mcp add --transport http openzeppelin-solidity https://mcp.openzeppelin.com/contracts/solidity/mcp

MCP Agentic Wallet — open-source session management for x402

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 Solidity Contracts has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of MCP Agentic Wallet — open-source session management for x402 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: MCP Agentic Wallet — open-source session management for x402 · 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.

Where the data comes from: how the catalog is built