Sato Hub
MCP

Hummingbot MCP

Official Hummingbot MCP server bridging agents to a Hummingbot API instance for multi-exchange trading.

  • Sato Score51
ActiveSelf-ReportedQuiet · 7mo ago

Hummingbot MCP is an open-source MCP server by Hummingbot Foundation, with last code activity on 2026-03-23 (Quiet). Latest release on 2025-10-06. Sato Score 51/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Hummingbot MCP →

Last commit Mar 23, 2026 · Last release Oct 6, 2025 · ★ 59

Listed from github.com/hummingbot/mcp on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch Hummingbot MCP

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on hummingbot/mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Hummingbot MCP connects Claude and Gemini CLI to a running Hummingbot API instance, exposing tools for account management, portfolio tracking, order placement, market data access, and bot deployment. Configured via a local server URL and credentials, it inherits Hummingbot's multi-exchange trading support.

Sato Score

51/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
18/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
11/15
Independent verification
2/10

Evidence — listed vs checked · what the words mean

Listed from github.com/hummingbot/mcp on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reportedgithub.com/hummingbot/mcpas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedgithub.com/hummingbot/mcpas of 2026-10-15
Recent activitylast release 2025-10-06 · last commit 2026-03-23observedgithub.com/hummingbot/mcp2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted: our container does not have `uv`, which the documented install needsself-reportedgithub.com/hummingbot/mcpas of 2026-09-21
Website answersanswered (HTTP 200)observedgithub.com/hummingbot/mcp2026-10-15
Daily check record89 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asDocker, Local (uv)confidence 0.85self-reportedgithub.com/hummingbot/mcpas of 2026-07-14
Works withClaude Code, Gemini CLIconfidence 0.85self-reportedgithub.com/hummingbot/mcpas of 2026-07-14
Sato Score51/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — not run by us — our container does not have `uv`, which the documented install needs

Runtime: python

git clone https://github.com/hummingbot/mcp
cd mcp && uv sync
{"mcpServers":{"hummingbot-mcp":{"type":"stdio","command":"uv","args":["--directory","/path/to/mcp","run","main.py"]}}}

You supply: A running Hummingbot API instance (separate self-hosted service, default http://localhost:8000), HUMMINGBOT_USERNAME + HUMMINGBOT_PASSWORD

Add to CursorAdd to VS Code
claude mcp add satohub-hummingbot-mcp -- uv --directory /path/to/mcp run main.py

A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-09-21. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

98.9%of 91 checks since 2026-07-17 succeeded
Currently responding for 24 days
Succeeded
90
Failed
1
Their error
0
Unattributed
1

State changed on 2026-09-21 (responding → unreachable from our probe), 2026-09-22 (unreachable from our probe → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
51
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Unknown
Agent types
MCP Server, Trading
Open source
Yes
Deploys as
Docker, Local (uv)
Works with
Claude Code, Gemini CLI
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#exchange#trading-bot#mcp-server#multi-exchange
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Hummingbot MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 22, 2026
    Sato Score tier: Low → Medium
    Score 37 → 51.
  2. Sep 21, 2026
    Sato Score tier: Medium → Low
    Score 52 → 37.
  3. Sep 21, 2026
    Verified: deploy spec
  4. Jul 18, 2026
    Sato Hub began tracking this listing
  5. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  6. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Hummingbot MCP

Is Hummingbot MCP open source?
Yes. Hummingbot MCP is open source under the Apache-2.0 license; the repository is https://github.com/hummingbot/mcp. Checked as of 2026-10-15.
Which chains does Hummingbot MCP support?
Sato Hub has no confirmed chain list for Hummingbot MCP as of 2026-10-15; treat chain support as unknown.
Is Hummingbot MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-03-23 (last commit 2026-03-23, last release 2025-10-06), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Hummingbot MCP?
python. Install: git clone https://github.com/hummingbot/mcp && cd mcp && uv sync. Entry: {"mcpServers":{"hummingbot-mcp":{"type":"stdio","command":"uv","args":["--directory","/path/to/mcp","run","main.py"]}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (uv --directory /path/to/mcp run main.py).
Is Hummingbot MCP verified on Sato Hub?
No independent verification is on record for Hummingbot MCP; its verification status is "Self-Reported" and its Sato Score is 51 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Hummingbot MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/hummingbot-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.