OpenZeppelin Stellar Contracts vs AssetFare USDC Bridge
OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). AssetFare USDC Bridge is an MCP server published by assetfare. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 Stellar Contracts |  AssetFare USDC Bridge |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.21.3 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 Stellar Contracts | AssetFare USDC Bridge |
|---|---|---|
| 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-12 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/stellar/mcp) | Remote server (api.assetfare.dev/mcp/bridge) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/assetfare/assetfare-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check | Responded 4 days ago | Responded 4 days 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 Stellar Contracts
Access to OpenZeppelin Stellar Contracts.
AssetFare USDC Bridge
Exact-amount top-two routing for six pilots; caller signs; AssetFare never signs or submits
How to run each
OpenZeppelin Stellar Contracts As a remote MCP server
claude mcp add --transport http openzeppelin-stellar https://mcp.openzeppelin.com/contracts/stellar/mcpAssetFare USDC Bridge As a remote MCP server
claude mcp add --transport http assetfare-bridge https://api.assetfare.dev/mcp/bridgeCommands 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 Stellar Contracts has
stellar-accountstellar-fungiblestellar-governorstellar-non-fungiblestellar-stablecoinstellar-vault
Only AssetFare USDC Bridge has
assetfare_manifestassetfare_v2_capabilitiesassetfare_v2_prepareassetfare_v2_quoteassetfare_v2_quote_selected_candidateassetfare_v2_route_selectionassetfare_v2_session_createassetfare_v2_session_getassetfare_v2_session_observe_outputassetfare_v2_session_observe_sourceassetfare_v2_session_refresh_action
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (AssetFare USDC Bridge as of 2026-10-16). 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 Stellar Contracts · What it can do: AssetFare USDC Bridge · 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.