Sato Hub
MCP

Fireblocks MCP Server

Fireblocks' open-source MCP server for its API: query vaults, assets, wallets and policies, and create transactions from an AI assistant.

  • ChainsMultichain
UnknownUnverified

No code activity tracked

Listed from developers.fireblocks.com on 2026-10-08. Install: not attempted — no install path on record. Not checked by Sato Hub yet: every row below is as listed. 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/mcp
Run Sato Hub Preflight on fireblocks/fireblocks-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

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.

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. Not checked by Sato Hub yet: every row below is as listed.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddevelopers.fireblocks.comas of 2026-10-08
Verification statusUnverified — not independently reviewedself-reporteddevelopers.fireblocks.comas of 2026-10-08

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.

Details

Chains
Multichain
Agent types
Wallet, Custody
Open source
Yes
Deploys as
npm, mcp server
Last checked
2026-10-08

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.

#mcp#custody#vaults#transactions#policies#fireblocks#ai-link
See something inaccurate or outdated?Submit a correction →

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

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-10-08.
Which chains does Fireblocks MCP Server support?
Fireblocks MCP Server lists support for Multichain as of 2026-10-08.
Is Fireblocks MCP Server still maintained?
Sato Hub tracks no commit or release for Fireblocks MCP Server; it cannot say whether it is maintained.
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". Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Fireblocks MCP Server — Sato Hub." Sato Hub, updated 2026-10-08, accessed 2026-10-08. https://satohub.ai/resources/fireblocks-mcp

Data last refreshed 2026-10-08; 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.