Ext Ops Panel
Open dashboard
Comparison

io.github.codespar/mcp-foxbit vs io.github.junct-bot/binance-mcp

io.github.codespar/mcp-foxbit is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.junct-bot/binance-mcp is an MCP server published by junct-bot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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-foxbitio.github.junct-bot/binance-mcp
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (npm): 124
Downloads/week (npm): 41
Forks (GitHub): 50
Stars (GitHub): 273
Not marked · First seen
Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 0
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-foxbit vs io.github.junct-bot/binance-mcp
Factio.github.codespar/mcp-foxbitio.github.junct-bot/binance-mcp
Marketplaces that list it11
Stars (GitHub) (differs)273 (better)0 (worse)
Forks (GitHub) (differs)50 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@codespar/mcp-foxbit)Remote server (binance.mcp.junct.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 2Not published
LicenceNot statedNot stated
Repository (differs)github.com/codespar/mcp-dev-latamgithub.com/junct-bot/binance-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-15

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-foxbit

In its own words, on Official MCP Registry:

MCP server for Foxbit — Brazilian crypto exchange, trading, orderbook, institutional

io.github.junct-bot/binance-mcp

In its own words, on Official MCP Registry:

Binance - 340 tools for market data, order books, and trading pairs

How to run each

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

Claude Code
claude mcp add --env "FOXBIT_API_KEY=<YOUR_FOXBIT_API_KEY>" --env "FOXBIT_API_SECRET=<YOUR_FOXBIT_API_SECRET>" --transport stdio mcp-foxbit -- npx -y @codespar/mcp-foxbit

Requires: FOXBIT_API_KEY (secret), FOXBIT_API_SECRET (secret)

io.github.junct-bot/binance-mcp As a remote MCP server

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

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

Only io.github.junct-bot/binance-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 io.github.junct-bot/binance-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.codespar/mcp-foxbit · What it can do: io.github.junct-bot/binance-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