Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs GDEX Trading

OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). GDEX Trading is an MCP server published by GemachDAO. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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 Stellar ContractsGDEX Trading
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.11.4
Downloads/month (npm): 737
Downloads/week (npm): 66
Forks (GitHub): 0
Stars (GitHub): 4
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 Stellar Contracts vs GDEX Trading
FactOpenZeppelin Stellar ContractsGDEX Trading
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)On your machine (@gemachdao/gdex-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)Not a bundle34
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/gemachdao/gdex-skill
Changes in the last 7 days (differs)05
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 Stellar Contracts

In its own words, on Docker MCP Catalog:

Access to OpenZeppelin Stellar Contracts.

GDEX Trading

In its own words, on Official MCP Registry:

GDEX (gdex.pro) trading for AI agents: spot, perps and HyperLiquid on Solana, EVM and more chains

How to run each

OpenZeppelin Stellar Contracts As a remote MCP server

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

GDEX Trading As a local MCP server: npm package

Claude Code
claude mcp add --env "GDEX_API_KEY=<YOUR_GDEX_API_KEY>" --transport stdio gdex-mcp-server -- npx -y @gemachdao/gdex-mcp-server

Requires: GDEX_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 GDEX Trading 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: GDEX Trading · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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