# Bitget

> Bitget is a centralised crypto exchange for spot, margin, futures, earn and tokenised stocks, reached through its Unified Trading Account v3 REST and WebSocket API and an Agent Hub toolkit with a stdio MCP server, CLI and agent skills.

- Canonical: https://www.anchorterminal.com/tools/bitget
- Pricing: https://www.anchorterminal.com/tools/bitget#pricing
- Reviews: https://www.anchorterminal.com/tools/bitget#reviews
- Markdown: https://www.anchorterminal.com/tools/bitget.md (~10,100 tokens)
- Slim: https://www.anchorterminal.com/tools/bitget.min.md (~2,580 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/bitget.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT bitget.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

## Overview

**Grade D · 53.9/100 · rank #890 of 1349 · #15 in Crypto exchanges · not agent-ready · confidence medium**


## Assessment

Bitget's official MCP server keeps the default surface to 14 intent tools with discovery, read-only and paper-trading switches, dry runs and a confirmation gate on withdrawals, over an API with demo trading. A 388 million dollar wallet breach in September 2026 paused withdrawals for eight days, and there is no status page, SLA or readable fee table.

## Facts

| Field | Value |
| --- | --- |
| Vendor | BTG Technology Holdings Limited (https://www.bitget.com) |
| Kind | HTTP API |
| Category | Crypto exchanges (https://www.anchorterminal.com/categories/crypto-exchanges) |
| Transport | stdio |
| Auth | API key · API key, system-generated secret and user-set passphrase minted under API Key Management after a browser sign-up and identity verification, up to 50 keys per UID, each with read or read-and-write permission, signed per request with HMAC-SHA256 or RSA over timestamp, method, path and body in the ACCESS-KEY, ACCESS-SIGN, ACCESS-TIMESTAMP and ACCESS-PASSPHRASE headers. Binding an IP is recommended, not required. Sub-account keys carry trade or management permission, read-only or read-write, once the main account enables key management for them. Demo keys are minted in demo mode and sent with the paptrading header set to 1 (https://www.bitget.com/legacy-docs/uta/guide, checked 2026-11-03). |
| Pricing | Pay per use (0.1% fee) · The API and the Agent Hub packages cost nothing; trades carry Bitget's fees. Base rates are 0.1 per cent maker and taker on spot and 0.02 per cent maker and 0.06 per cent taker on futures before VIP tiers or the BGB discount, which applies to spot only at a rate the article says to read on the live schedule. The fee page draws its table by script (https://www.bitget.com/support/articles/12560603892734, 20 August 2026, checked 2026-11-03). |
| x402 | No · No x402, MPP or L402 in the UTA docs, the Agent Hub READMEs, the SDK's openapi.yaml or the fee article (checked 2026-11-03). |
| Licence | unknown |
| Tools exposed | 14 |
| Packages | npm: `@bitget-ai/bitget-agent-mcp`; npm: `bitget-mcp-server` |
| MCP registry name | `io.github.Bitget-AI/bitget-agent-mcp` |
| Source | https://github.com/Bitget-AI/agent-mcp |
| Docs | https://www.bitget.com/api-doc/uta/intro |
| llms.txt | not found |
| Last release | 2026-10-30 |
| GitHub stars | 234 (as of 2026-11-03) |
| Surface listed | The Unified Trading Account v3 REST and WebSocket API at api.bitget.com, read from bitget.com/legacy-docs (the api-doc site renders only its overview for our reader), the support centre, the Agent Hub page, the Bitget-AI and BitgetLimited GitHub accounts, npm and the MCP registry on 3 November 2026. No account was made, no key minted and no MCP session opened |
| MCP server | Official, two generations. `@bitget-ai/bitget-agent-mcp` 3.3.1 (github.com/Bitget-AI/agent-mcp, MIT, stdio, Node 20) over the UTA v3 API: 14 tools by default (market, order, position, strategy_order, account_overview, account_config, repayment, transfer_funds, deposit, withdraw, funds_records, subaccount, discover, raw; loan and tax with their modules), `--surface full` adds one tool per endpoint, annotations derived from a read, write or high risk level. In the official MCP registry as io.github.Bitget-AI/bitget-agent-mcp 3.0.2. The Agent Hub page on bitget.com still documents `bitget-mcp-server` 1.1.0 (58 tools in 9 modules over the V2 API, maintainer digmouse, repository under a personal account). No hosted endpoint |
| Key permissions | Read or read-and-write per key, up to 50 keys per UID, passphrase set by the user and not recoverable, IP binding recommended. Sub-account keys with unified account trade or management permission, each read-only or read-write, once the main account enables API key management. No separate withdrawal or transfer permission appears in the docs read; the Agent Hub READMEs tell users to disable withdrawal access, so the management page may offer it |
| Rate limits | 6,000 requests per IP per minute on api.bitget.com, limits per endpoint per UID rising with VIP level (10 a second default, 60 at VIP 1, 80 at VIP 2, 100 at VIP 3 to 7), REST and WebSocket sharing quota, x-mbx-used-remain-limit on responses. WebSocket 300 connection requests per IP per 5 minutes and 100 connections per IP. The error code for a breach was not read; the agent SDK backs off and retries on 429 |
| Testnet and demo | Demo trading on api.bitget.com with a demo API key and the paptrading header set to 1, WebSocket at wss://wspap.bitget.com/v3/ws/public and /private. The MCP server's --paper-trading flag adds the header |
| Fees | Base spot 0.1 per cent maker and taker, base futures 0.02 per cent maker and 0.06 per cent taker, before VIP tiers; BGB offsets spot fees at a rate shown on the live schedule, which draws by script |
| FIX and WebSocket | No FIX API in the docs read. WebSocket public and private channels at ws.bitget.com with order placement and modification over the socket, an SBE feed for institutions, and preview notices for snapshot changes dated for demo and live |
| Countries | The terms' Prohibited Countries are Austria, Belarus, Canada, Cuba, France, Germany, Hong Kong, Iran, Japan, Kazakhstan, Malaysia, North Korea, Russia, Singapore, Sudan, the United States with its territories and outlying islands, Iraq, Libya, Yemen, Afghanistan, the Central African Republic, the Democratic Republic of the Congo, Guinea-Bissau, Haiti, Lebanon, Somalia, South Sudan, Thailand, and the Crimea, Luhansk, Donetsk, Kherson and Zaporizhzhia regions of Ukraine, plus any location Bitget designates |
| Terms on automated trading | Clause 11.1(ix) bars deep linking, web crawlers, bots, spiders and other automatic devices used to obtain or copy platform content, and 11.1(xiv)(c) bars bypassing robot exclusion headers; API keys are treated as account credentials and no clause limits API trading. Clause 13.1 disclaims continuous access and clause 16.1 caps liability at three months of fees |
| Security incident | On 24 September 2026 at 18:31 UTC forged withdrawal commands from a compromised internal credential moved about 388 million dollars in 13 assets on 11 chains from 12 hot and warm wallet addresses; withdrawals blocked at 19:05 and signing shut at 21:44, root cause found 25 September, Mandiant and SlowMist reports 30 September, BTC withdrawals back 28 September and all assets, fiat and C2C by 2 October. Private keys and cold wallets not affected per Bitget; the Protection Fund was topped above 300 million dollars |
| Other agent surfaces | `bgc` CLI (bitget-agent-cli) with read-only and paper-trading modes, bitget-agent-skill for Claude Code, Codex and OpenClaw, bitget-signal market-analysis skills needing no key, bitget-agent-installer, and official SDKs in Java, Python, Node.js, Go and PHP under BitgetLimited/v3-bitget-api-sdk |
| Legal entity | BTG Technology Holdings Limited per the terms and the privacy notice, Hong Kong law and HKIAC arbitration; the privacy notice applies the Seychelles Data Protection Act 2023 and names BTGT Europe Limited, UAB as EEA representative. Press releases are datelined Victoria, Seychelles |
| Capabilities | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto |
| Tags | hosted, closed-source, api-key, usage-priced, sandbox, no-status-page, mcp, mcp-registry, official, read-only-mode, agent-skills, cli, python, typescript, go, java, php |
| JSON | https://www.anchorterminal.com/api/v1/tools/bitget.json |

## Score breakdown (methodology v0.7, October 2026 research run)

Assessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 40 | 8.0 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 74 | 12.0 |
| Agent ergonomics | 13% | 16.2 | 83 | 13.5 |
| Security & auth | 14% | 17.5 | 62 | 10.8 |
| Payments & pricing | 10% | 12.5 | 40 | 5.0 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 78 | 6.8 |
| Transparency & trust (editorial 53, provenance 76) | 7% | 8.8 | 65 | 5.7 |
| Negative events | up to −15 | up to −15 | Security incident of 24 September 2026. An attacker who had obtained high-level internal credentials through a vulnerability in a third-party security product injected forged withdrawal commands into Bitget's wallet back end and moved about 388 million dollars in 13 assets on 11 chains from hot and warm wallets. Withdrawals, fiat and C2C were paused from 24 September and restored in phases from 28 September to 2 October 2026; trading, deposits and the API kept running. Bitget says user balances were unaffected, the Protection Fund covered the loss and was topped above 300 million dollars, private keys and cold wallets were untouched, and Mandiant and SlowMist reports of 30 September agree with its account. A fixed, documented incident with a public root cause, so below the top of the range. Sources https://www.bitget.com/academy/12560603896113 (updated 20 October 2026) and https://www.bitget.com/support/articles/12560603896110 (26 September 2026), read 2026-11-03.  | -8 |
| **Total** | | | | **53.9 → D** |

### Why each score

- Reliability 40 (checked 2026-11-03): Graded with the hosted lines on the UTA v3 API at api.bitget.com. No status page found (status.bitget.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history; the September 2026 breach is in the deduction, not here. Rate limits are published as 6,000 per IP per minute and per-endpoint UID limits by VIP level (15). An x-mbx-used-remain-limit header is documented and the agent SDK backs off on 429, orders take a clientOid of up to 64 characters, but the breach error code and a Retry-After rule were not read (10 of 15). No SLA (0). UTA v3 is the production API (10). 40.
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 74 (checked 2026-11-03): The agent SDK ships openapi.yaml with 109 typed UTA v3 operations from which the tools are generated, a machine-readable contract from the vendor's own organisation though not on the docs site (20 of 25). llms.txt in the SDK and MCP repositories; the docs site has none (6 of 10). Intent tools with a discover tool that explains each verb, action and its risk level, and the server's initialize instructions state surface, modules and read-only posture (15 of 20). Typed inputs with enums and required fields from the OpenAPI source (12 of 15). Examples in the quick start and READMEs, a REST error code page in the legacy docs that we did not read in full (9 of 15). Changelog by day with preview notices and effective dates (12 of 15). 74.
- Agent ergonomics 83 (checked 2026-11-03): Read for the API with the MCP server as the agent route. 14 compact tools by default, module filters, a full surface on request and progressive discovery (25). Cursor pagination on CFD order history since 15 October 2026 and limit parameters on lists (15 of 20). Uniform ok or error result shape from the SDK with typed error classes and compact JSON in the text channel (13 of 20). clientOid on orders, `dryRun: true` on every write, `confirm: true` gating cancelAll and withdraw, annotations derived from risk level including readOnlyHint, destructiveHint and idempotentHint (18 of 20). Few required fields, official SDKs in five languages plus the TypeScript agent SDK and a CLI (12 of 15). 83.
- Security & auth 62 (checked 2026-11-03): API keys with read or read-and-write permission, a passphrase, HMAC-SHA256 or RSA signing, IP binding recommended, 50 keys per UID, revocation on the management page; no OAuth and no separate withdrawal scope in the docs read (22 of 30). --read-only strips write tools at start, --paper-trading routes to demo, and high-risk writes need `confirm: true` (18 of 20). Tools return the exchange's own data (10). Request and response hooks are forwarded as MCP log notifications; no per-call audit log on Bitget's side was found (6 of 15). security@bitget.com in the toolkit README, no security.txt, Mandiant and SlowMist reports on the September breach, a proof-of-reserves repository, no bounty page read (6 of 20). 62.
- Payments & pricing 40 (checked 2026-11-03): No machine payment protocol (0). Base spot and futures rates are stated in a help article without login, the tier table draws by script (20). Market data needs no key, demo trading costs nothing and no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 40.
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 78 (checked 2026-11-03): Read as a hosted service with an open-source toolkit. The UTA changelog's latest launched entry is 30 October 2026 and a preview entry 3 November; the MCP package shipped 3.3.1 on 20 September and agent-skill was pushed 30 October (30). 58 dated changelog entries since 5 August 2026 and six MCP versions since June (20). Issue trackers on the Bitget-AI repositories (11 open on agent_hub) and a support centre; replies were not checked (10 of 25). In the official MCP registry under io.github.Bitget-AI, a GitHub namespace, with official SDKs in five languages (10 of 15). CI workflow with coverage, npm provenance attestations, two runtime dependencies, no install scripts (8 of 10). 78.
- Transparency & trust 65 (checked 2026-11-03): The editorial half. A closed hosted service with clear terms naming BTG Technology Holdings Limited; the toolkit is MIT (15 of 30). The privacy notice names the controller and EEA representative, gives 7-year and up to 10-year retention for compliance and litigation, and names recipients by category only (18 of 30). Deprecations and parameter changes carry effective dates (delta mode deprecated 27 August, symbol and category required from 30 September, snapshot changes with demo and live dates) but no written policy (15 of 20). Recipients by category, transfers under Seychelles law with no locations or provider names (5 of 20). 53.

Fix list, everything this grade says the listing lacks, the biggest gain first (20 items). What it covers is at https://www.anchorterminal.com/fixes/bitget.md (JSON https://www.anchorterminal.com/fixes/bitget.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "bitget", "plan": "read"}`, free while the beta runs

### What we couldn't check

- unchecked: the current api-doc site (every path answered the UTA overview), the REST error code page in full, the rate-limit breach code and any Retry-After rule, and the API management page's permission options beyond read and read-and-write, so a withdrawal scope may exist that the docs read do not show.
- unchecked: the fee tier table and the BGB discount rate (script-drawn), issue responsiveness on the Bitget-AI repositories, and the tools as served by the MCP server (no session opened; counts from the README, server.json and source).
- Two official servers. The Agent Hub page on bitget.com documents bitget-mcp-server 1.1.0 (V2 API, 58 tools, repository under a personal GitHub account, maintainer digmouse) while GitHub and npm carry @bitget-ai/bitget-agent-mcp 3.3.1 (UTA v3). The listing grades the v3 server, which the Agent Hub README calls the current one. Recorded as drift, not deducted.
- Deduction -8 for the September 2026 breach, a security incident within 12 months, fixed and documented with a public root cause and third-party reports, user balances covered per Bitget, so below the top of the range.
- Kind http-api, because the docs lead with the UTA REST and WebSocket API and the MCP server is stdio only, one package in the Agent Hub toolkit.
- firstReleased is 2018-10-19, the creation date of the oldest repository in the BitgetLimited account (WebSocket-JAVA-Demo); Bitget's blog says the exchange was established in 2018 without a day.
- Our own products. It doesn't do LocalGhost's or letme's job; it is one exchange's trading API. Graded the normal way.

### Sources

- robots.txt: <https://www.bitget.com/robots.txt> (seen 2026-11-03)
- UTA quick start, legacy docs (hosts, headers, signing, keys, demo trading, rate limits, SDKs): <https://www.bitget.com/legacy-docs/uta/guide> (seen 2026-11-03)
- VIP rate limit rules, legacy docs: <https://www.bitget.com/legacy-docs/uta/rate-limit/> (seen 2026-11-03)
- UTA changelog, legacy docs: <https://www.bitget.com/legacy-docs/uta/changelog> (seen 2026-11-03)
- api-doc site (answers the UTA overview for every path): <https://www.bitget.com/api-doc/uta/intro> (seen 2026-11-03)
- Agent Hub MCP page on bitget.com (bitget-mcp-server, 58 tools, links to Bitget-AI/agent_hub): <https://www.bitget.com/en/activity-hub/agent-hub/mcp> (seen 2026-11-03)
- Support article, Agent Hub upgrade with skills and CLI (9 March 2026): <https://www.bitget.com/support/articles/12560603867888> (seen 2026-11-03)
- agent-mcp README: <https://raw.githubusercontent.com/Bitget-AI/agent-mcp/main/README.md> (seen 2026-11-03)
- agent-mcp and agent-sdk source, server.json, CHANGELOG, openapi.yaml, CI workflow, shallow clones: <https://github.com/Bitget-AI/agent-mcp> (seen 2026-11-03)
- agent_hub README: <https://raw.githubusercontent.com/Bitget-AI/agent_hub/main/README.md> (seen 2026-11-03)
- Bitget-AI GitHub organisation and repositories: <https://api.github.com/orgs/Bitget-AI/repos?per_page=100&sort=updated> (seen 2026-11-03)
- npm registry, @bitget-ai/bitget-agent-mcp (versions, maintainer, scripts): <https://registry.npmjs.org/@bitget-ai%2fbitget-agent-mcp> (seen 2026-11-03)
- npm registry, bitget-mcp-server (versions, maintainer): <https://registry.npmjs.org/bitget-mcp-server> (seen 2026-11-03)
- official MCP registry search: <https://registry.modelcontextprotocol.io/v0/servers?search=bitget> (seen 2026-11-03)
- Terms of Use (20 October 2026): <https://www.bitget.com/support/articles/360014944032-terms-of-use> (seen 2026-11-03)
- Privacy notice (5 December 2025): <https://www.bitget.com/support/articles/360015150651> (seen 2026-11-03)
- Trading fees FAQ (20 August 2026): <https://www.bitget.com/support/articles/12560603892734> (seen 2026-11-03)
- Bitget hack explained, timeline and response (27 September 2026, updated 20 October): <https://www.bitget.com/academy/12560603896113> (seen 2026-11-03)
- Support notice, withdrawals resumed in phases (26 September 2026): <https://www.bitget.com/support/articles/12560603896110> (seen 2026-11-03)
- RDAP for bitget.com: <https://rdap.verisign.com/com/v1/domain/bitget.com> (seen 2026-11-03)
- security.txt (404): <https://www.bitget.com/.well-known/security.txt> (seen 2026-11-03)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/bitget/history.json

- 2026-11-03: graded 53.9 D (methodology 0.7)

## Who's behind it (provenance 76/100, checked 2026-11-03)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | BTG Technology Holdings Limited | 20/20 |
| Domain age | bitget.com, registered 2003-02-03 (23 years) | 15/15 |
| Endpoint on the vendor's domain | bitget.com | 15/15 |
| Terms of service | read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points | 5.1/10 |
| Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 |
| Status page | not found | 0/10 |
| Changelog | published | 10/10 |
| security.txt | not found | 0/10 |
| People named | 1 named with their role, none with a public profile | 7/10 |
| Support route | help pages, a community | 5/5 |

Terms of Use last updated 20 October 2026 name BTG Technology Holdings Limited under Hong Kong law with HKIAC arbitration; the privacy notice (5 December 2025) names the same company as controller under the Seychelles Data Protection Act 2023 with BTGT Europe Limited, UAB as EEA representative. /user-agreement and /privacy-policy answer 404; the documents live in the support centre.

www.bitget.com/robots.txt disallows internal, search, calendar, wiki and register paths; the api-doc, legacy-docs, support, academy, blog and activity-hub paths are allowed.

RDAP gives bitget.com a registration date of 3 February 2003 (MarkMonitor), earlier than the exchange, so the domain was bought.

https://www.bitget.com/.well-known/security.txt answers 404; the Agent Hub README gives security@bitget.com for reports. No status page found; status.bitget.com does not resolve and the docs link none.

The current api-doc site answers every path with the UTA overview for a reader without script; the legacy docs at /legacy-docs/uta/ were read for the guide, rate limits and changelog.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://www.bitget.com/support/articles/360014944032-terms-of-use), read 2026-11-03, dated 2026-10-20, states 6 of the 7 things a reader expects.

- To know. Restricts automated access (costs points). "(ix) (a) use any deep linking, web crawlers, bots, spiders or other automatic devices, programs, scripts, algorithms or methods, or any similar or equivalent manual processes to access, obtain, copy or monitor any part of the Platform"
- To know. Says the terms or the service can change without notice (costs points). "8.1 Bitget may at any time modify, suspend or discontinue any portion or feature of the Services without prior notice to or any consent from you and without assigning any reason for that action."
- To know. Says access can be ended without notice or for any reason. "If you decline to provide the requested information, or otherwise do not comply in a timely manner, we reserve the right to suspend or terminate your access to your Account, or to all or part of the Services immediately, without notice."
- To know. Requires arbitration or waives class actions. "Without prejudice to the generality of the foregoing, you agree that claims shall be resolved exclusively by way of binding arbitration;"
- Gives the date it was last updated. Last updated 2026-10-20.
- Says how changes to the terms are announced. Says it gives notice of a change.
- Not found in the text. Refers to a service level or uptime commitment.
- Also in the text (2026-11-03). Liability is capped at the fees the customer paid to Bitget in the three months before the event, and only for gross negligence, wilful misconduct, fraud or material continuing breach. "Bitget and its Affiliates will not be liable to you for any amounts in aggregate exceeding the total amount of fees paid by you to Bitget in the three (3) month period immediately preceding the event giving rise to the loss."
- Also in the text (2026-11-03). Any IP rights the customer creates under the terms, including User Materials, are assigned to Bitget on the day they are created. "The User-created IP Rights shall automatically vest in us on the date on which it is created."
- Also in the text (2026-11-03). The Services may not be used for resale or commercial purposes, including transactions on behalf of other persons or entities, unless Bitget agrees in writing. "(ii) use Services for resale or commercial purposes, including transactions on behalf of other persons or entities, unless expressly agreed by us in writing;"

**Privacy policy** (https://www.bitget.com/support/articles/360015150651), read 2026-11-03, dated 2025-12-05, states 7 of the 8 things a reader expects.

- Gives the date it was last updated. Last updated 2025-12-05.
- Says how long data is kept. For as long as needed, with no period named.
- Not found in the text. Says whether personal data is sold or shared for advertising.
- Gives a privacy contact. Names a data protection officer.
- Says where data is transferred or stored. Relies on standard contractual clauses.

## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)

### Key people

- Gracy Chen, Chief Executive Officer, Bitget, since May 2024
- Note: Bitget's about page answered 404, so the role comes from Bitget's blog post of 21 May 2024 announcing Gracy Chen as CEO, which also says the exchange was established in 2018 and names Sandra Lou as the chief executive she succeeded without giving Lou's title or calling her a founder. No founder is named on a page we read, so the roster is incomplete. The terms of use name BTG Technology Holdings Limited under Hong Kong law and the privacy notice names the same company under the Seychelles Data Protection Act; no page read states who owns it, so ownership is recorded as unknown. Investors were looked for on the blog, in the terms and in two web searches; Dragonfly's 10 million dollar strategic investment of April 2023 is reported by The Block and Fortune and recorded, while earlier rounds named only by aggregators (Consensus Labs and Collinstar Capital in 2018, Anlan Capital and SNK in 2020) are left out.
- BTG Technology Holdings Limited: LinkedIn https://www.linkedin.com/company/bitget-global/ X https://x.com/bitgetglobal GitHub https://github.com/Bitget-AI

### Ownership and investors

- Backed by: Dragonfly

### Getting support

- Discord: https://discord.com/invite/bitget
- Help: https://www.bitget.com/support
- Help: https://www.bitget.com/en/activity-hub/agent-hub/mcp
- Community (Bitget on Telegram): https://t.me/BitgetENOfficial
- Community (Agent Hub issues): https://github.com/Bitget-AI/agent_hub/issues
- General contact: security@bitget.com
- General contact: legal@bitget.com
- General contact: dpo@bitget.com
- Sources: https://www.bitget.com/blog/articles/bitget-appoints-gracy-chen-as-ceo, https://www.bitget.com/support/articles/360014944032-terms-of-use, https://www.bitget.com/support/articles/360015150651, https://www.bitget.com/support/articles/12560603896110, https://raw.githubusercontent.com/Bitget-AI/agent_hub/main/README.md, https://www.theblock.co/post/224702/dragonfly-invests-bitget

## Live (updated 2026-11-04 17:11 UTC)

- mcp-registry `io.github.Bitget-AI/bitget-agent-mcp` 3.0.2
- security.txt: none
- Always current: https://www.anchorterminal.com/api/v1/live/bitget.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Prices

| Item | Price | Unit | Note |
| --- | --- | --- | --- |
| Spot trade, base maker or taker | 0.1% | percentage fee | before VIP tiers and the BGB discount |
| Futures trade, base taker | 0.06% | percentage fee | maker 0.02 per cent |

Across all listings: https://www.anchorterminal.com/prices/index.md

## Strengths

- Official stdio MCP server with 14 intent tools by default, progressive discovery, `--read-only`, `--paper-trading`, `dryRun: true` on writes and `confirm: true` required for withdrawals and cancel-all
- Demo trading on the production host with demo keys and a paptrading header, and a TypeScript agent SDK whose openapi.yaml types all 109 UTA v3 operations
- Terms name BTG Technology Holdings Limited with Hong Kong law, and the privacy notice gives retention periods of 7 and up to 10 years
- Changelog with 58 dated entries since 5 August 2026, including preview notices with demo and live dates for WebSocket changes
- Base fees public in a help article, 0.1 per cent spot and 0.02 per cent maker and 0.06 per cent taker on futures

## Weaknesses

- Hot and warm wallets lost about 388 million dollars on 24 September 2026 to forged withdrawal commands, and withdrawals were paused until 2 October
- No status page, incident history or SLA; the terms disclaim uninterrupted access
- Two official MCP servers coexist, the V2-based bitget-mcp-server on Bitget's own Agent Hub page and the v3 bitget-agent-mcp on GitHub and npm, with different tool counts
- The current api-doc site renders every page as the UTA overview for a reader without script; the legacy docs were used instead
- Keys have read or read-and-write only, with no separate withdrawal permission in the docs read, and IP binding is recommended rather than required



## Before you call it (notes for agents)

1. Run `npx -y @bitget-ai/bitget-agent-mcp --read-only` for research and `--paper-trading` with a demo key before any live order; the two flags cannot be combined
2. Call discover({}) first, then the intent verbs; add `dryRun: true` to any write to preview it, and pass `confirm: true` only after the person has agreed to a withdraw or cancelAll
3. Send a unique clientOid of at most 64 characters on every order and reuse it on retry; orderId wins when both are sent
4. Stay under 10 requests a second per endpoint on a new account and 6,000 a minute per IP; the SDK retries on 429, so do not add a second retry loop
5. Bind the key to an IP and keep write permission off a research key; the docs read show no separate withdrawal scope

## Connect

Install:

```bash
npx -y @bitget-ai/bitget-agent-mcp
```

First request:

```bash
curl https://api.bitget.com/api/v3/market/tickers?category=SPOT&symbol=BTCUSDT
```

Claude Code:

```bash
claude mcp add bitget -- npx -y @bitget-ai/bitget-agent-mcp --read-only
```

MCP client configuration:

```json
{
  "mcpServers": {
    "bitget": {
      "args": [
        "-y",
        "@bitget-ai/bitget-agent-mcp",
        "--read-only"
      ],
      "command": "npx",
      "env": {
        "BITGET_API_KEY": "YOUR_API_KEY",
        "BITGET_PASSPHRASE": "YOUR_PASSPHRASE",
        "BITGET_SECRET_KEY": "YOUR_SECRET_KEY"
      }
    }
  }
}
```

Through letme: https://letme.dev/bitget. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Gemini Exchange API | BB | 74.6 | 70 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/gemini-exchange.md |
| Kraken API | BB | 71 | 159 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/kraken.md |
| OKX API | B | 64.3 | 413 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/okx.md |
| Binance API | B | 63.2 | 448 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/binance.md |
| Bitfinex API | C | 58.4 | 687 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bitfinex.md |
| Bybit | C | 57.3 | 745 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bybit.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- Official MCP server `@bitget-ai/bitget-agent-mcp` 3.3.1 (npm, MIT, stdio, 20 September 2026) from github.com/Bitget-AI/agent-mcp, a thin adapter over `@bitget-ai/bitget-agent-sdk` with 14 intent tools by default (12 verbs plus discover and raw) over 89 UTA v3 operations, `--surface full` for one tool per endpoint, `--modules`, `--read-only`, `--paper-trading` for the demo environment, `dryRun: true` on every write and `confirm: true` required for cancelAll and withdraw (source: <https://raw.githubusercontent.com/Bitget-AI/agent-mcp/main/README.md>)
- Bitget's own Agent Hub page documents the earlier server `bitget-mcp-server` 1.1.0 (58 tools in 9 modules over the V2 API, npm, 17 March 2026) and links github.com/Bitget-AI/agent_hub, which ties the Bitget-AI GitHub organisation to the exchange; a support article of 9 March 2026 announced the Agent Hub upgrade with skills and a CLI (source: <https://www.bitget.com/en/activity-hub/agent-hub/mcp and https://www.bitget.com/support/articles/12560603867888>)
- In the official MCP registry as io.github.Bitget-AI/bitget-agent-mcp 3.0.2 (17 August 2026), a GitHub namespace, stdio with BITGET_API_KEY, BITGET_SECRET_KEY and BITGET_PASSPHRASE as secrets (source: <https://registry.modelcontextprotocol.io/v0/servers?search=bitget>)
- Rate limits of 6,000 requests per IP per minute on the common domain, per-endpoint UID limits that rise with VIP level (10 a second by default, 60 at VIP 1, 100 at VIP 3 and above) and an x-mbx-used-remain-limit response header; REST and WebSocket share the quota (source: <https://www.bitget.com/legacy-docs/uta/guide and https://www.bitget.com/legacy-docs/uta/rate-limit/>)
- Demo trading through demo keys and the paptrading: 1 header on api.bitget.com, with WebSocket at wspap.bitget.com; the agent SDK's openapi.yaml (109 operations) documents clientOid up to 64 characters on orders (source: <https://www.bitget.com/legacy-docs/uta/guide>)
- On 24 September 2026 an attacker with internal credentials obtained through a third-party product injected forged withdrawal commands and moved about 388 million dollars from hot and warm wallets; withdrawals, fiat and C2C paused and resumed in phases from 28 September to 2 October, trading and deposits ran throughout, and Bitget says user balances were unaffected and the Protection Fund covered the loss (source: <https://www.bitget.com/academy/12560603896113, updated 20 October 2026>)
- Terms of Use (BTG Technology Holdings Limited, last updated 20 October 2026, Hong Kong law, HKIAC arbitration) list about 30 prohibited countries including the United States, Canada, Japan, Singapore, Hong Kong, France, Germany, Austria, Malaysia, Thailand and Russia, and bar bots and automated devices that copy platform content (source: <https://www.bitget.com/support/articles/360014944032-terms-of-use>)

- #15 of 21 in Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md
- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md

## Compare

- [Bitfinex API vs Bitget](https://www.anchorterminal.com/compare/bitfinex-vs-bitget.md): C 58.4 vs D 53.9
- [Bitget vs Bithumb Open API](https://www.anchorterminal.com/compare/bitget-vs-bithumb.md): D 53.9 vs D 50.6
- [Bitget vs Bitstamp API](https://www.anchorterminal.com/compare/bitget-vs-bitstamp.md): D 53.9 vs D 50.4
- [Bitget vs Bybit](https://www.anchorterminal.com/compare/bitget-vs-bybit.md): D 53.9 vs C 57.3
- [Bitget vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.md): D 53.9 vs C 61.7
- [Bitget vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.md): D 53.9 vs C 60
- [Bitget vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.md): D 53.9 vs D 46.8
- [Bitget vs Deribit](https://www.anchorterminal.com/compare/bitget-vs-deribit.md): D 53.9 vs C 59
- [Bitget vs dYdX](https://www.anchorterminal.com/compare/bitget-vs-dydx.md): D 53.9 vs B 69.5
- [Bitget vs Gate](https://www.anchorterminal.com/compare/bitget-vs-gate-io.md): D 53.9 vs C 56.4
- [Bitget vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.md): D 53.9 vs BB 74.6
- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md): D 53.9 vs E 43.3
- [Bitget vs Hyperliquid](https://www.anchorterminal.com/compare/bitget-vs-hyperliquid.md): D 53.9 vs D 50
- [Bitget vs Kraken API](https://www.anchorterminal.com/compare/bitget-vs-kraken.md): D 53.9 vs BB 71
- [Bitget vs KuCoin](https://www.anchorterminal.com/compare/bitget-vs-kucoin.md): D 53.9 vs D 53.9
- [Bitget vs MEXC API](https://www.anchorterminal.com/compare/bitget-vs-mexc.md): D 53.9 vs C 56.3
- [Bitget vs OKX API](https://www.anchorterminal.com/compare/bitget-vs-okx.md): D 53.9 vs B 64.3
- [Bitget vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitget-vs-uniswap.md): D 53.9 vs B 63.3
- [Bitget vs Upbit Open API](https://www.anchorterminal.com/compare/bitget-vs-upbit.md): D 53.9 vs C 54.7
- [Binance API vs Bitget](https://www.anchorterminal.com/compare/binance-vs-bitget.md): B 63.2 vs D 53.9

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on bitget.com or one of its subdomains, or the README at the root of github.com/Bitget-AI/agent-mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "bitget", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/bitget"><img src="https://www.anchorterminal.com/badges/bitget.svg" alt="Bitget on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Bitget on Anchor Terminal](https://www.anchorterminal.com/badges/bitget.svg)](https://www.anchorterminal.com/tools/bitget)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/bitget">Bitget on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Bitget is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/bitget-dark.png
- Light: https://www.anchorterminal.com/assets/share/bitget-light.png

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
