BitGo MCP
BitGo's official Developer Portal MCP for natural-language search over its institutional wallet API docs.
- Sato Score61
- ChainsMultichain
BitGo MCP is a MCP server by BitGo, with no code activity tracked. Sato Score 61/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 BitGo MCP →No code activity tracked
Listed from bitgo.com on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch BitGo MCP
One email if what we observe changes — its endpoint stops answering, 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 https://developers.bitgo.com/mcp 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
BitGo MCP is an official MCP server hosted at developers.bitgo.com/mcp by BitGo, an institutional digital asset custody and wallet infrastructure provider. It exposes documentation search and retrieval across BitGo's API guides and blockchain reference content covering wallets, staking, trading, and webhooks — it does not perform live wallet operations. An agent builder plugs it into IDE or chat clients to ground answers in current BitGo API documentation.
Sato Score
61/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 0/20
- Interface verifiability
- 10/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 3/10
Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).
Evidence — listed vs checked · what the words mean
Listed from bitgo.com on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | developers.bitgo.com | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | bitgo.com | as of 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted by Sato Hub | self-reported | developers.bitgo.com | as of 2026-07-20 |
| MCP endpoint answers | answered — 11 tools listed | observed | developers.bitgo.com | 2026-10-15 |
| Daily check record | 90 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 |
| Sato Score | 61/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 — as documented by the project, not run by us
Runtime: Hosted MCP endpoint (no local install)
claude mcp add bitgo-docs --transport http https://developers.bitgo.com/mcp
{"mcpServers": {"BitGo Docs": {"type": "http", "url": "https://developers.bitgo.com/mcp"}}}You supply: None documented — this server is a documentation assistant over public BitGo docs, not a wallet-control API
claude mcp add --transport http satohub-bitgo-mcp https://developers.bitgo.com/mcp
A remote server: your client connects to the project's endpoint. 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-20. What a deploy spec is →
Tool inventory — 11 tools, probed live 2026-10-15
execute-request— Execute an API request (HAR request object) against BitGo. The request is validated against a known endpoint before it is proxied.fetch— Fetch the full markdown content of a documentation page by the id returned from 'search' or 'search-releases'. Section ids resolve to their parent page.get-cookbook— Get one cookbook by slug (from search-cookbooks): its summary, ordered steps, and the API endpoints it calls. Full code samples are on the linked url.get-endpoint— Get details for one endpoint. Returns a resolved view by default (parameters + request/response schemas); pass format="openapi" for a self-contained OpenAPI fragment.list-specs— List the available OpenAPI specs. Use a spec id (or title) with 'get-endpoint' and 'execute-request'.protect-client-secrets— Returns BitGo's secret-handling guidance. This server serves documentation only and never handles real credentials; always use placeholder values in code.search— Search BitGo documentation. Scope defaults to sections and returns bounded passages with an id, title, url, and parent page context; set scope="pages" for one result per full page. Limit defaults to 8search-cookbooks— Search the BitGo cookbook catalog — end-to-end integration walkthroughs. Limit defaults to 8 and is capped at 25; results include steps and the API calls they make.search-endpoints— Search across all OpenAPI specs for endpoints matching a pattern (case-insensitive, over path, method, summary, and operationId). Limit defaults to 10 and is capped at 60; results group by spec and fesearch-releases— Search BitGo release notes and changelog entries, newest first. Use for 'what's new', 'latest release', or 'recent changes' questions; each result includes its publication date. Omit the query to listsecurity-reminder— Returns BitGo's security guidance for AI-assisted development. Call at the start of a session and whenever credentials are referenced.
- Answers a handshake
- yes · 2026-10-15
- Answers a call
- yes — list-specs returned in 106 ms
Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
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.
Tool inventory history — 11 now, peak 11, since 2026-07-19
- 2026-09-10 10 → 11 +1 (search-releases)
- 2026-07-21 10 → 10 +2 (get-cookbook, search-cookbooks) −2 (get-recipe, search-recipes)
Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.
Details
- Chains
- Multichain
- Agent types
- MCP Server, Data Provider
- Open source
- Unknown
- 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 BitGo MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to BitGo MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 20, 2026Edited: mcp endpoint url
- Jul 20, 2026Edited: deploy spec
- Jul 19, 2026Edited: mcp endpoint url
- Jul 19, 2026Sato Score tier: Low → MediumScore 32 → 57.
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about BitGo MCP
- Is BitGo MCP open source?
- Unknown. Sato Hub has not found a public repository or a license statement for BitGo MCP as of 2026-10-15.
- Which chains does BitGo MCP support?
- BitGo MCP lists support for Multichain as of 2026-10-15.
- Is BitGo MCP still maintained?
- Sato Hub tracks no commit or release for BitGo MCP; it cannot say whether it is maintained.
- How do I install or run BitGo MCP?
- Hosted MCP endpoint (no local install). Install: claude mcp add bitgo-docs --transport http https://developers.bitgo.com/mcp. Entry: {"mcpServers": {"BitGo Docs": {"type": "http", "url": "https://developers.bitgo.com/mcp"}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://developers.bitgo.com/mcp (HTTP)).
- Is BitGo MCP verified on Sato Hub?
- Sato Hub holds one earned check for BitGo MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 61 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. "BitGo MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/bitgo-mcpData 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.