Ext Ops Panel
Open dashboard
Comparison

io.github.hummingbot/mcp vs io.github.junct-bot/jupiter-mcp

io.github.hummingbot/mcp is an MCP server published by hummingbot. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.junct-bot/jupiter-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-18. 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.hummingbot/mcpio.github.junct-bot/jupiter-mcp
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 40
Stars (GitHub): 59
Not marked · First seen
Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:053c4df31f68
Forks (GitHub): 40
Stars (GitHub): 59
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

io.github.hummingbot/mcp vs io.github.junct-bot/jupiter-mcp
Factio.github.hummingbot/mcpio.github.junct-bot/jupiter-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)59 (better)0 (worse)
Forks (GitHub) (differs)40 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (docker.io/hummingbot/hummingbot-mcp:0.1.0)Remote server (jupiter.mcp.junct.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)21Not published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/hummingbot/mcpgithub.com/junct-bot/jupiter-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.hummingbot/mcp

In its own words, on Official MCP Registry:

MCP server exposing Hummingbot API for automated multi-exchange trading

io.github.junct-bot/jupiter-mcp

In its own words, on Official MCP Registry:

Jupiter - 4 tools for swap quotes, liquidity pools, and trading data

How to run each

io.github.hummingbot/mcp As a local MCP server: Docker image

Claude Code
claude mcp add --env "HUMMINGBOT_API_URL=<YOUR_HUMMINGBOT_API_URL>" --env "HUMMINGBOT_PASSWORD=<YOUR_HUMMINGBOT_PASSWORD>" --env "HUMMINGBOT_USERNAME=<YOUR_HUMMINGBOT_USERNAME>" --transport stdio io-github-hummingbot-mcp -- docker run -i --rm -e HUMMINGBOT_API_URL -e HUMMINGBOT_PASSWORD -e HUMMINGBOT_USERNAME docker.io/hummingbot/hummingbot-mcp:0.1.0

Requires: HUMMINGBOT_API_URL, HUMMINGBOT_PASSWORD (secret), HUMMINGBOT_USERNAME (secret)

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

Claude Code
claude mcp add --transport http jupiter-mcp https://jupiter.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/jupiter-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.junct-bot/jupiter-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.junct-bot/jupiter-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.hummingbot/mcp · What it can do: io.github.junct-bot/jupiter-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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