Ext Ops Panel
Open dashboard
Comparison

GDEX Trading vs io.github.luziadev/luzia

GDEX Trading is an MCP server published by GemachDAO. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.luziadev/luzia is an MCP server published by luziadev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplaceGDEX Tradingio.github.luziadev/luzia
Official MCP Registry Listed
Version: 5.4.1
Downloads/month (npm): 1 571
Downloads/week (npm): 788
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Listed
Version: 1.3.0
Downloads/month (npm): 293
Downloads/week (npm): 72
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 5.4.1
Downloads/month (npm): 1 571
Downloads/week (npm): 788
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed

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

GDEX Trading vs io.github.luziadev/luzia
FactGDEX Tradingio.github.luziadev/luzia
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-11-06Not published
Where it runs (differs)On your machine (@gemachdao/gdex-mcp-server)Remote server (mcp.luzia.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/gemachdao/gdex-skillgithub.com/luziadev/mcp-server
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 404

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

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

io.github.luziadev/luzia

In its own words, on Official MCP Registry:

Real-time crypto prices from Binance, Coinbase, Kraken, OKX, and Bybit

How to run each

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)

io.github.luziadev/luzia As a remote MCP server

Claude Code
claude mcp add --transport http luzia https://mcp.luzia.dev/mcp

Requires: LUZIA_API_KEY (secret)

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

Only io.github.luziadev/luzia has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only GDEX Trading asks for

  • GDEX_API_KEY (secret)
  • GDEX_API_URL

Only io.github.luziadev/luzia asks for

  • LUZIA_API_KEY (secret)

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

What it can do: GDEX Trading · What it can do: io.github.luziadev/luzia · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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