io.github.hummingbot/mcp vs PineForge — offline PineScript v6 backtest 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). PineForge — offline PineScript v6 backtest MCP is an MCP server published by pineforge-4pass. 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
| Marketplace |  io.github.hummingbot/mcp |  PineForge — offline PineScript v6 backtest MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 40 Stars (GitHub): 59 Not marked · First seen |
Listed Version: 0.9.18 Forks (GitHub): 1 Stars (GitHub): 7 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 | PineForge — offline PineScript v6 backtest MCP |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 59 (better) | 7 (worse) |
| Forks (GitHub) (differs) | 40 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (docker.io/hummingbot/hummingbot-mcp:0.1.0) | On your machine (ghcr.io/pineforge-4pass/pineforge-codegen-mcp:v0.9.18) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 21 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/hummingbot/mcp | github.com/pineforge-4pass/pineforge-codegen-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
PineForge — offline PineScript v6 backtest MCP
Offline PineScript v6 → C++ backtests at deterministic TradingView parity, run locally via MCP.
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)
PineForge — offline PineScript v6 backtest MCP As a local MCP server: Docker image
claude mcp add --transport stdio pineforge-codegen-mcp -- docker run -i --rm ghcr.io/pineforge-4pass/pineforge-codegen-mcp:v0.9.18Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of PineForge — offline PineScript v6 backtest MCP publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of PineForge — offline PineScript v6 backtest 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: PineForge — offline PineScript v6 backtest 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.