OpenZeppelin Stellar Contracts vs Veriql Risk
OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Veriql Risk is an MCP server published by veriql.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  Veriql Risk |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Downloads/month (npm): 1 052 Downloads/week (npm): 374 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 | Veriql Risk |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-10-31 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/stellar/mcp) | On your machine (veriql-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 12 h ago | no 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 Stellar Contracts
Access to OpenZeppelin Stellar Contracts.
Veriql Risk
Rug, honeypot and wallet-approval risk checks on Solana and EVM, with every penalty driver shown.
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/mcpVeriql Risk As a local MCP server: npm package
claude mcp add --env "VERIQL_API_KEY=<YOUR_VERIQL_API_KEY>" --transport stdio veriql-mcp -- npx -y veriql-mcpRequires: VERIQL_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only OpenZeppelin Stellar Contracts has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Veriql Risk publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of OpenZeppelin Stellar Contracts publish no settings it asks for, so we do not compare settings.
What it can do: OpenZeppelin Stellar Contracts · What it can do: Veriql Risk · 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.