Ext Ops Panel
Open dashboard
Comparison

QuantConnect vs GDEX Trading

QuantConnect is an MCP server published by QuantConnect. 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-15. 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
MarketplaceQuantConnectGDEX Trading
Docker MCP Catalog Listed
Version: sha256:f96cc99e83a0
Forks (GitHub): 33
Pulls (Docker Hub): 36 169
Stars (Docker Hub): 1
Stars (GitHub): 79
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.11.3
Downloads/month (npm): 723
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

QuantConnect vs GDEX Trading
FactQuantConnectGDEX Trading
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)79 (better)4 (worse)
Pulls (Docker Hub) (differs)36 169No figure on Docker Hub
Forks (GitHub) (differs)33 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/quantconnect)On your machine (@gemachdao/gdex-mcp-server)
Transportstdiostdio
Tools it declares (differs)64Not published
Environment variables it asks for (differs)3, secrets among them: 02, secrets among them: 1
Parts of the bundle (differs)Not a bundle1
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/quantconnect/mcp-servergithub.com/gemachdao/gdex-skill
Changes in the last 7 days (differs)02
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

QuantConnect

In its own words, on Docker MCP Catalog:

The QuantConnect MCP Server is a bridge for AIs (such as Claude and OpenAI o3 Pro) to interact with our cloud platform. When equipped with our MCP, the AI can perform tasks on your behalf through our API such as updating projects, writing strategies, backtesting, and deploying strategies to production live-trading.

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

QuantConnect As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio quantconnect -- docker run -i --rm mcp/quantconnect

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 QuantConnect asks for

  • AGENT_NAME
  • QUANTCONNECT_API_TOKEN
  • QUANTCONNECT_USER_ID

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: QuantConnect · 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