Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs Trading Signals

OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Trading Signals is an MCP server published by roman-rr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 ContractsTrading Signals
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
Forks (GitHub): 15
Stars (GitHub): 124
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 Trading Signals
FactOpenZeppelin Stellar ContractsTrading Signals
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub124
Forks (GitHub) (differs)No figure on GitHub15
Last release (differs)Not published2026-10-12
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)Remote server (signals.x70.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/roman-rr/trading-skills
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agoResponded 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.

Trading Signals

In its own words, on Official MCP Registry:

Live AI crypto trading signals for agents. Try 3 signals without a key; sign in from your agent.

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

Trading Signals As a remote MCP server

Claude Code
claude mcp add --transport http trading-signals https://signals.x70.ai/mcp

Commands 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

The marketplaces of Trading Signals publish no list of tools, so we do not compare tools.

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: Trading Signals · 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