Ext Ops Panel
Open dashboard
Comparison

Maestro vs GDEX Trading

Maestro is an MCP server published by maestro-org. 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: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceMaestroGDEX Trading
Docker MCP Catalog Listed
Version: sha256:00309c887383
Forks (GitHub): 3
Pulls (Docker Hub): 31 750
Stars (Docker Hub): 1
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 5.1.0
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

Maestro vs GDEX Trading
FactMaestroGDEX Trading
Marketplaces that list it11
Stars (GitHub) (differs)25 (better)4 (worse)
Pulls (Docker Hub) (differs)31 750No figure on Docker Hub
Forks (GitHub) (differs)3 (better)0 (worse)
Last release (differs)Not published2026-10-19
Where it runs (differs)On your machine (mcp/maestro-mcp-server)On your machine (@gemachdao/gdex-mcp-server)
Transportstdiostdio
Tools it declares (differs)35Not published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/maestro-org/maestro-mcp-servergithub.com/gemachdao/gdex-skill
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11

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

Maestro

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) server exposing Bitcoin blockchain data through the Maestro API platform. Provides tools to explore blocks, transactions, addresses, inscriptions, runes, and other metaprotocol data.

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

Maestro As a local MCP server: Docker image

Claude Code
claude mcp add --env "API_KEY_API_KEY=<YOUR_API_KEY_API_KEY>" --transport stdio maestro-mcp-server -- docker run -i --rm -e API_KEY_API_KEY mcp/maestro-mcp-server

Requires: API_KEY_API_KEY (secret)

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.

Tools each declares

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

Settings each asks for

Only Maestro asks for

  • API_KEY_API_KEY (secret)

Only GDEX Trading asks for

  • GDEX_API_KEY (secret)
  • GDEX_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Maestro · 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