Bitget Agent Hub
Official Bitget toolkit: MCP server, CLI, SDK, and skills for spot, futures, and account operations.
- Sato Score60
Bitget Agent Hub is an open-source MCP server by Bitget, with last code activity on 2026-06-30 (Quiet). Sato Score 60/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 Bitget Agent Hub →Last commit Jun 30, 2026 · ★ 229
Listed from github.com/Bitget-AI/agent_hub on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch Bitget Agent Hub
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/mcpRun Sato Hub Preflight on bitget-ai/agent_hub before I use it.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
Bitget's official open-source agent ecosystem bundles bitget-agent-mcp (MCP server for desktop AI clients), bitget-agent-cli (terminal tool), bitget-agent-sdk (89 UTA v3 operations), and bitget-agent-skill (a reasoning guide for the CLI), plus bitget-signal for keyless market analysis. Covers spot orders, leveraged futures, account management, and transfers, with read-only and paper-trading modes for rehearsal.
Sato Score
60/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 19/20
- Interface verifiability
- 8/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 11/15
- Independent verification
- 2/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v3.3.1 · as of 2026-09-26- Does it take your key?
- No key read found
- Does your key leave?
- Not observed
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from github.com/Bitget-AI/agent_hub on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | not stated | self-reported | github.com/Bitget-AI/agent_hub | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | github.com/Bitget-AI/agent_hub | as of 2026-10-15 |
| Recent activity | last commit 2026-06-30 | observed | github.com/Bitget-AI/agent_hub | 2026-10-15 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/Bitget-AI/agent-mcp | 2026-07-21 |
| Website answers | answered (HTTP 200) | observed | github.com/Bitget-AI/agent_hub | 2026-10-15 |
| Daily check record | 89 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-09-26 |
| Key leaves the machine | not observed during install and start-uplater or triggered code paths are not covered | observed | satohub.ai | 2026-09-26 |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-26 |
| Deploys as | npm/npx (CLI and MCP packages), meta-installer (bitget-agent-installer)confidence 0.85 | self-reported | github.com/Bitget-AI/agent_hub | as of 2026-07-14 |
| Works with | Claude Code, Claude Desktop, Cursor, Codex, ChatGPT, OpenClaw, Windsurf, Contin…confidence 0.90 | self-reported | github.com/Bitget-AI/agent_hub | as of 2026-07-14 |
| Sato Score | 60/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-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 — reproduced in a container Jul 21, 2026
Runtime: node
npx -y @bitget-ai/bitget-agent-mcp npx -y @bitget-ai/bitget-agent-mcp
You supply: BITGET_API_KEY, BITGET_SECRET_KEY, BITGET_PASSPHRASE (Bitget API key with Read + Trade permissions)
claude mcp add satohub-bitget-agent-hub -- npx -y @bitget-ai/bitget-agent-mcp
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-07-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- 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
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
- Pricing
- Free (MIT license)
- Deploys as
- npm/npx (CLI and MCP packages), meta-installer (bitget-agent-installer)
- Works with
- Claude Code, Claude Desktop, Cursor, Codex, ChatGPT, OpenClaw, Windsurf, Continue
- 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.
Where Bitget Agent Hub fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets
Listing History
Recorded changes to Bitget Agent Hub's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 30, 2026Sato Score tier: High → MediumScore 73 → 63.
- Jul 21, 2026Verified: deploy spec
- Jul 20, 2026Sato Score tier: Medium → HighScore 65 → 73.
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Auto-enriched: deployment options, supported integrations
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Phantom MCP
ActivePhantom's MCP server that lets AI agents view addresses, sign transactions, swap, and transfer tokens across Solana, Ethereum, Bitcoin, and Sui.
Bankless Onchain MCP
UnknownMCP server providing AI assistants read access to onchain data via the Bankless API.
Jupiter MCP Server
ActiveOpen-source MCP servers that let AI agents execute Solana token swaps via Jupiter's Ultra aggregation API.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Bitget Agent Hub
- Is Bitget Agent Hub open source?
- Yes. Bitget Agent Hub is open source under the MIT license; the repository is https://github.com/Bitget-AI/agent_hub. Checked as of 2026-10-15.
- Which chains does Bitget Agent Hub support?
- Sato Hub has no confirmed chain list for Bitget Agent Hub as of 2026-10-15; treat chain support as unknown.
- Is Bitget Agent Hub still maintained?
- The most recent code activity Sato Hub observed was on 2026-06-30 (last commit 2026-06-30), 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 Bitget Agent Hub?
- node. Install: npx -y @bitget-ai/bitget-agent-mcp. Entry: npx -y @bitget-ai/bitget-agent-mcp. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y @bitget-ai/bitget-agent-mcp).
- Is Bitget Agent Hub verified on Sato Hub?
- Sato Hub holds one earned check for Bitget Agent Hub: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 60 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Bitget Agent Hub — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/bitget-agent-hubData 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.