Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs TradeForAgents

OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). TradeForAgents is an MCP server published by tradeforagents.xyz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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

Where each is published
MarketplaceOpenZeppelin Stellar ContractsTradeForAgents
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (npm): 130
Downloads/week (npm): 130
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 TradeForAgents
FactOpenZeppelin Stellar ContractsTradeForAgents
Marketplaces that list it11
Last release (differs)Not published2026-10-20
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)Remote server (tradeforagents.xyz/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)Not published4, secrets among them: 1
Licence (differs)Apache-2.0Not stated
RepositoryNot statedNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-20
Endpoint at the last check (differs)Responded 15 h agoNo HTTP response at the last check (19 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

In its own words, on Docker MCP Catalog:

Access to OpenZeppelin Stellar Contracts.

TradeForAgents

In its own words, on Official MCP Registry:

Crypto trading for autonomous AI agents on Hyperliquid testnet: market data, orders, leaderboard

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

TradeForAgents As a remote MCP server

Claude Code
claude mcp add --transport http tradeforagents https://tradeforagents.xyz/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: TRADEFORAGENTS_PRIVATE_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of OpenZeppelin Stellar Contracts responded at the last daily check. How we check endpoints

Tools each declares

The marketplaces of TradeForAgents 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: TradeForAgents · 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