io.github.hummingbot/mcp vs MoltNode by Chord
io.github.hummingbot/mcp is an MCP server published by hummingbot. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). MoltNode by Chord is an MCP server published by tuantqse90. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. 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
| Marketplace |  io.github.hummingbot/mcp |  MoltNode by Chord |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 40 Stars (GitHub): 59 Not marked · First seen |
Listed Version: 1.1.4 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | io.github.hummingbot/mcp | MoltNode by Chord |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 59 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 40 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (docker.io/hummingbot/hummingbot-mcp:0.1.0) | Remote server (moltnode.ag/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 21 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/hummingbot/mcp | github.com/tuantqse90/moltnode-mcp |
| Changes in the last 7 days (differs) | 0 | 7 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
MCP server exposing Hummingbot API for automated multi-exchange trading
MoltNode by Chord
Read 31 blockchains over JSON-RPC and swap via Chord: best route, unsigned tx, simulation. No key.
How to run each
io.github.hummingbot/mcp As a local MCP server: Docker image
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.0Requires: HUMMINGBOT_API_URL, HUMMINGBOT_PASSWORD (secret), HUMMINGBOT_USERNAME (secret)
MoltNode by Chord As a remote MCP server
claude mcp add --transport http moltnode https://moltnode.ag/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of MoltNode by Chord publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of MoltNode by Chord publish no settings it asks for, so we do not compare settings.
What it can do: io.github.hummingbot/mcp · What it can do: MoltNode by Chord · 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. 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.