Ext Ops Panel
Open dashboard
Comparison

io.github.codespar/mcp-bitso vs Gate Exchange MCP

io.github.codespar/mcp-bitso is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). Gate Exchange MCP is an MCP server published by gateio-dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceio.github.codespar/mcp-bitsoGate Exchange MCP
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (npm): 148
Downloads/week (npm): 45
Forks (GitHub): 50
Stars (GitHub): 272
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 22
Stars (GitHub): 42
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

io.github.codespar/mcp-bitso vs Gate Exchange MCP
Factio.github.codespar/mcp-bitsoGate Exchange MCP
Marketplaces that list it11
Stars (GitHub) (differs)272 (better)42 (worse)
Forks (GitHub) (differs)50 (better)22 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@codespar/mcp-bitso)Remote server (api.gatemcp.ai/mcp/exchange)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/codespar/mcp-dev-latamgithub.com/gate/gate-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (11 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

io.github.codespar/mcp-bitso

In its own words, on Official MCP Registry:

MCP server for Bitso — Latin American crypto exchange, trading, funding, withdrawals

Gate Exchange MCP

In its own words, on Official MCP Registry:

OAuth Gate exchange MCP for CEX trading, account, wallet, unified account, and sub-account.

How to run each

io.github.codespar/mcp-bitso As a local MCP server: npm package

Claude Code
claude mcp add --env "BITSO_API_KEY=<YOUR_BITSO_API_KEY>" --transport stdio mcp-bitso -- npx -y @codespar/mcp-bitso

Requires: BITSO_API_KEY (secret)

Gate Exchange MCP As a remote MCP server

Claude Code
claude mcp add --transport http gate-exchange https://api.gatemcp.ai/mcp/exchange

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

Only Gate Exchange MCP 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

The marketplaces of Gate Exchange MCP publish no settings it asks for, so we do not compare settings.

What it can do: io.github.codespar/mcp-bitso · What it can do: Gate Exchange MCP · Compare two other plugins

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