OpenZeppelin Stellar Contracts vs OrionCMD Checks
OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). OrionCMD Checks is an MCP server published by api.orioncmd.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.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 Stellar Contracts | OrionCMD Checks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/stellar/mcp) | Remote server (api.orioncmd.com/mcp) |
| 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 | Not stated | Not stated |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 2 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 Stellar Contracts
Access to OpenZeppelin Stellar Contracts.
OrionCMD Checks
Pay-per-call TLS certificate, DNS/email-auth and domain-expiry checks for any domain (x402 USDC).
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/mcpOrionCMD Checks As a remote MCP server
claude mcp add --transport http checks https://api.orioncmd.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only OrionCMD Checks has a remote endpoint we check. How we check endpoints
Tools each declares
Only OpenZeppelin Stellar Contracts has
stellar-accountstellar-fungiblestellar-governorstellar-non-fungiblestellar-stablecoinstellar-vault
Only OrionCMD Checks has
check_certcheck_dnscheck_domain_expirycheck_email_authcheck_security_headersdomain_gradepricingsite_healthvalidate_target
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (OrionCMD Checks as of 2026-10-13). 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: OrionCMD Checks · 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.