Fireblocks MCP Server
Fireblocks' open-source MCP server for its API: query vaults, assets, wallets and policies, and create transactions from an AI assistant.
- Sato Score60
- ChainsMultichain
Fireblocks MCP Server is an open-source MCP server by Fireblocks, with last code activity on 2025-09-04 (Dormant). Latest release on 2025-09-04. Sato Score 60/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-22. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Sep 4, 2025 · Last release Sep 4, 2025 · ★ 10
Listed from developers.fireblocks.com on 2026-10-08. Install: not attempted — no install path on record. Evidence →
Next step
Watch Fireblocks MCP Server
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 fireblocks/fireblocks-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
The fireblocks/fireblocks-mcp repo (npm @fireblocks/mcp-server, MIT) exposes Fireblocks API operations to an MCP client: vault accounts and assets, exchange accounts, network connections, policies, external and internal wallets, workspace users, and transaction create and query. It needs a Fireblocks API key and secret file from an existing workspace. Fireblocks' build-with-AI page also lists AI Link (early access through Fireblocks Labs, with a remote read-only and a local read-write MCP) and a hosted docs MCP. What the agent can do is whatever the API key's role and your Fireblocks policy allow.
Sato Score
60/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 18/20
- Interface verifiability
- 8/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 9/15
- Independent verification
- 5/10
Evidence — listed vs checked · what the words mean
Listed from developers.fireblocks.com on 2026-10-08. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | developers.fireblocks.com | as of 2026-11-22 |
| Verification status | Unverified — not independently reviewed | self-reported | developers.fireblocks.com | as of 2026-11-22 |
| Recent activity | last release 2025-09-04 · last commit 2025-09-04 | observed | github.com/fireblocks/fireblocks-mcp | 2026-11-22 |
| Website answers | answered (HTTP 200) | observed | developers.fireblocks.com | 2026-11-22 |
| Daily check record | 44 of 44 daily checks since 2026-10-09 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-11-21 |
| Works with | Claude Desktop, Cursorconfidence 0.90 | self-reported | github.com/fireblocks/fireblocks-mcp | as of 2026-10-10 |
| Sato Score | 60/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-11-22 |
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.
Observed record — 45 daily checks since 2026-10-09
- Succeeded
- 45
- 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.
Last 30 days — to 2026-11-22, 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
- Multichain
- Agent types
- Wallet, Custody
- Open source
- Yes
- Deploys as
- npm, mcp server
- Works with
- Claude Desktop, Cursor
- Last checked
- 2026-11-22
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 Fireblocks MCP Server fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Fireblocks MCP Server's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 10, 2026Auto-enriched: supported integrations
- Oct 9, 2026Sato Hub began tracking this listing
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 Fireblocks MCP Server
- Is Fireblocks MCP Server open source?
- Yes. Fireblocks MCP Server is open source; the repository is https://github.com/fireblocks/fireblocks-mcp. Checked as of 2026-11-22.
- Which chains does Fireblocks MCP Server support?
- Fireblocks MCP Server lists support for Multichain as of 2026-11-22.
- Is Fireblocks MCP Server still maintained?
- The most recent code activity Sato Hub observed was on 2025-09-04 (last commit 2025-09-04, last release 2025-09-04), which Sato Hub labels "Dormant". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Fireblocks MCP Server?
- Sato Hub has no deploy spec for Fireblocks MCP Server; follow the project's own documentation at https://github.com/fireblocks/fireblocks-mcp.
- Is Fireblocks MCP Server verified on Sato Hub?
- No independent verification is on record for Fireblocks MCP Server; its verification status is "Unverified" and its Sato Score is 60 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Fireblocks MCP Server — Sato Hub." Sato Hub, updated 2026-11-22, accessed 2026-11-22. https://satohub.ai/resources/fireblocks-mcpData last refreshed 2026-11-22; 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.