Fuse Network
@fuseio
About Fuse Network
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"fuse": {
"url": "https://mcp.fuse.io/mcp"
}
}
}Tools
50Returns the native FUSE balance for an address, or an ERC-20 token balance when `tokenAddress` is supplied.
Fetches a transaction by hash. Returns null if the transaction is not found.
Fetches the receipt for a mined transaction (status, gasUsed, logs). Returns null if the transaction is pending or unknown.
Calls a view/pure function on a Fuse contract. ABI is auto-fetched from the verified Fuse explorer when not supplied.
Reads name, symbol, decimals, and totalSupply for an ERC-20 token deployed on Fuse.
Returns the current Fuse network gas price (in wei and gwei) along with EIP-1559 fee suggestions when available.
Resolves an ENS name to its EVM address. ENS is not deployed on Fuse — resolution requires `ENS_RPC_URL` to be configured (typically pointing at Ethereum mainnet). Plain hex addresses are passed through.
Reads ERC-4337 state for a smart account on Fuse: deployment status, EntryPoint nonce, and the account's deposit balance at the EntryPoint. Paymaster eligibility is not evaluated in v0.1.
Lists all ERC-20 tokens held by a wallet on Fuse, enriched with Fusebox metadata (symbol, decimals, USD value). Powered by the Fusebox SDK BalancesModule.
Lists all NFTs (ERC-721 / ERC-1155 collectibles) owned by a wallet on Fuse. Powered by the Fusebox SDK BalancesModule.
Lists every staking option supported by Fuse — token, APR, TVL, expiry, and the matching unstake token. Powered by the Fusebox SDK StakingModule.
Returns the active staking positions for a wallet — staked amount, USD value, earned rewards, and APR per position. Powered by the Fusebox SDK StakingModule.
Returns the current USD price for an ERC-20 token tracked by Fusebox. Powered by the Fusebox SDK TradeModule.
Returns the 24-hour percentage price change for an ERC-20 token tracked by Fusebox. Powered by the Fusebox SDK TradeModule.
Returns OHLC / interval price stats for an ERC-20 token over a week, month, or year. Powered by the Fusebox SDK TradeModule.
Returns the catalogue of ERC-20 tokens tracked by Fusebox (tradable, indexed, priced). Powered by the Fusebox SDK TradeModule.
Quotes a token swap on Fuse — expected output amount, route, and price impact. Read-only: returns the quote without submitting a trade. Powered by the Fusebox SDK TradeModule.
Returns the ERC-4337 UserOperation history for a smart account on Fuse, indexed via the Fusebox GraphQL service. Powered by the Fusebox SDK GraphQLModule.
Create a Fusebox Notification webhook for a project. Requires `FUSEBOX_SECRET_API_KEY` (Notification API endpoints authenticate with both apiKey and API-SECRET).
Retrieve details of a single Fusebox Notification webhook. Requires `FUSEBOX_SECRET_API_KEY`.
List every Fusebox Notification webhook configured for a given project. Requires `FUSEBOX_SECRET_API_KEY`.
Update a Fusebox Notification webhook's URL or event type. Requires `FUSEBOX_SECRET_API_KEY`.
Permanently delete a Fusebox Notification webhook. Destructive — the webhook stops receiving events. Requires `FUSEBOX_SECRET_API_KEY`.
Add one or more EVM addresses to a webhook's listening scope. Requires `FUSEBOX_SECRET_API_KEY`.
Remove EVM addresses from a webhook's listening scope. Requires `FUSEBOX_SECRET_API_KEY`.
List every EVM address monitored by a given webhook. Requires `FUSEBOX_SECRET_API_KEY`.
Exchange an EIP-191 signature for a JWT used as Bearer auth on Smart Wallet API calls (e.g. `fuse_smart_wallet_get_actions`). Signing happens client-side; this tool only submits the signed payload.
List the paginated action history (transfers, contract calls) of an authenticated smart wallet. The JWT comes from `fuse_smart_wallet_authenticate`.
Returns an indicative price + route for a swap on Fuse (0x-style response). One of `sellAmount` / `buyAmount` must be provided.
Returns the liquidity sources currently enabled for Fuse-chain trades (e.g. voltage.finance, sub-pools).
Returns a token's price change over a custom day-count window (`{ priceChange, currentPrice, previousPrice }`).
Generic dispatcher for the Fusebox Explorer API (`/api/v0/explorer/`). Pass `module` + `action` + any additional query params. Covers all 40+ etherscan-compatible endpoints including balances, logs, transactions, contract ABI/source, and the five contract-verify POST routes.
Returns the EOA address controlled by the server's configured `FUSE_PRIVATE_KEY`. Use this before any write tool to confirm which account will pay gas and send transactions.
Submits a signed transaction transferring native FUSE from the server's signer to a recipient. Returns the transaction hash; use `fuse_get_receipt` to confirm inclusion.
Submits a signed `ERC20.transfer(to, amount)` from the server's signer. Decimals are auto-fetched from the token; use `unit: "base"` to skip scaling.
Signs and submits a state-mutating contract call from the server's signer. ABI is auto-fetched from the Fuse explorer when not supplied. Returns the transaction hash.
Signs and submits a contract-deployment transaction using the server's signer. Returns the transaction hash, and the deployed contract address when `waitForReceipt: true`.
Signs a message with the server's signer using EIP-191 (`personal_sign`). Returns the 65-byte signature as hex. No on-chain transaction is submitted.
Signs a structured EIP-712 payload with the server's signer. Returns the 65-byte signature as hex. No on-chain transaction is submitted.
Returns the ERC-4337 smart-wallet address derived from the configured signer, plus whether the Fuse paymaster (gasless mode) is enabled.
Submits an ERC-4337 UserOperation transferring a token (native FUSE or ERC-20) from the configured smart wallet. Gasless when `FUSE_USE_PAYMASTER=true`.
Submits an ERC-4337 UserOperation transferring an NFT (ERC-721 / ERC-1155) from the configured smart wallet to a recipient.
Submits an ERC-4337 UserOperation calling `ERC20.approve(spender, amount)` from the configured smart wallet.
Submits an ERC-4337 UserOperation calling `approve(spender, tokenId)` on an NFT contract from the configured smart wallet.
Atomically approves a token and invokes a follow-up call on the spender from the configured smart wallet. Common DeFi pattern.
Submits an ERC-4337 UserOperation invoking arbitrary calldata on a contract from the configured smart wallet. Use when you need full control over the encoded call.
Submits a single ERC-4337 UserOperation that executes a sequence of contract calls atomically. Failed sub-calls revert the whole batch.
Submits an ERC-4337 UserOperation executing a swap on Fuse via the Fusebox trade engine. Quote a swap first with `fuse_get_trade_quote` to preview the route.
Submits an ERC-4337 UserOperation that stakes a token using Fuse's staking module. List options first with `fuse_get_staking_options`.
Submits an ERC-4337 UserOperation that unstakes a token via Fuse's staking module.
Overview
What is Fuse Network?
Fuse Network is a Model Context Protocol (MCP) server for the Fuse blockchain. It lets AI agents (such as Claude, Cursor, and Gemini) read on‑chain data, submit account‑abstracted transactions, deploy contracts, and operate Fusebox APIs through a single standard tool interface. It can be used via a free hosted read‑only endpoint or by self‑hosting an instance that provides full write capabilities.
How to use Fuse Network?
The hosted endpoint is available at https://mcp.fuse.io/mcp using the Streamable HTTP transport. Point your MCP‑compatible agent at that URL – no setup beyond adding the server to the agent’s configuration. To enable write tools (e.g. sending transactions, deploying contracts), you must self‑host the server via Docker or node dist/index.js, setting the required environment variables (FUSE_PRIVATE_KEY, FUSEBOX_PUBLIC_API_KEY, etc.).
Key features of Fuse Network
- 50 tools across five categories: RPC reads, SDK reads, REST APIs, EOA writes, and smart‑account writes.
- RPC reads work without any API key; all other categories require one or more environment‑configured keys.
- Self‑hosted instance offers full write access; hosted endpoint is read‑only.
- Supports ERC‑4337 smart‑account UserOps, including gasless transactions via the Fuse paymaster.
- Private keys are only read from the environment at startup and never accepted as tool arguments.
Use cases of Fuse Network
- Read Fuse blockchain balances, transactions, and contract state without an API key.
- Query token prices, staking options, portfolio data, and UserOp history through Fusebox SDK tools.
- Send native FUSE, transfer ERC‑20 tokens, execute arbitrary contract calls, and deploy contracts from an EOA.
- Build gasless user experiences by submitting ERC‑4337 UserOps through the Fuse paymaster.
- Interact with Fusebox REST APIs for notifications, smart wallet authentication, trades, and explorer queries.
FAQ from Fuse Network
How does the hosted endpoint differ from self‑hosting?
The hosted endpoint (https://mcp.fuse.io/mcp) is read‑only because it does not have a private key configured. Write tools return an actionable error pointing you to self‑hosting. Self‑hosted instances can perform all 50 tools, including transactions and contract deployment, because you control the private key.
What dependencies or runtime are required?
Self‑hosting requires Node.js (for direct execution) or Docker. Environment variables such as FUSE_PRIVATE_KEY, FUSEBOX_PUBLIC_API_KEY, and FUSEBOX_SECRET_API_KEY must be set. No special hardware is needed; the server can run on a typical Linux, macOS, or Windows machine.
Where do my data and transactions live?
The hosted endpoint reads public data from the Fuse blockchain and Fusebox APIs. Self‑hosted instances run locally on your infrastructure – all signing and transaction submission happens on your own server. The README advises treating the self‑hosted server as a hot‑wallet signer and locking down ingress.
What are the known limits of the hosted endpoint?
The hosted endpoint is rate‑limited for fair sharing and cannot execute any write tools. The Fusebox public key bundled there is also subject to rate limits. To perform writes or obtain higher rate limits, you must self‑host.
Which transports and authentication methods are supported?
The hosted endpoint uses Streamable HTTP (POST with optional SSE upgrade) and requires no authentication. Self‑hosted servers can run on stdio (for local subprocess clients) or HTTP (configurable via MCP_TRANSPORT). Authentication for self‑hosted instances is provided through environment‑configured API keys and the private key.
Frequently asked questions
How does the hosted endpoint differ from self‑hosting?
The hosted endpoint (`https://mcp.fuse.io/mcp`) is read‑only because it does not have a private key configured. Write tools return an actionable error pointing you to self‑hosting. Self‑hosted instances can perform all 50 tools, including transactions and contract deployment, because you control the private key.
What dependencies or runtime are required?
Self‑hosting requires Node.js (for direct execution) or Docker. Environment variables such as `FUSE_PRIVATE_KEY`, `FUSEBOX_PUBLIC_API_KEY`, and `FUSEBOX_SECRET_API_KEY` must be set. No special hardware is needed; the server can run on a typical Linux, macOS, or Windows machine.
Where do my data and transactions live?
The hosted endpoint reads public data from the Fuse blockchain and Fusebox APIs. Self‑hosted instances run locally on your infrastructure – all signing and transaction submission happens on your own server. The README advises treating the self‑hosted server as a hot‑wallet signer and locking down ingress.
What are the known limits of the hosted endpoint?
The hosted endpoint is rate‑limited for fair sharing and cannot execute any write tools. The Fusebox public key bundled there is also subject to rate limits. To perform writes or obtain higher rate limits, you must self‑host.
Which transports and authentication methods are supported?
The hosted endpoint uses Streamable HTTP (POST with optional SSE upgrade) and requires no authentication. Self‑hosted servers can run on stdio (for local subprocess clients) or HTTP (configurable via `MCP_TRANSPORT`). Authentication for self‑hosted instances is provided through environment‑configured API keys and the private key.
Basic information
More Other MCP servers
🪟 Windows-MCP
CursorTouchMCP Server for Computer Use in Windows
AutoBrowser MCP
autobrowser-aiBrowser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
MCP Go 🚀
mark3labsA Go implementation of the Model Context Protocol (MCP), enabling seamless integration between LLM applications and external data sources and tools.
DeepMark
DeepMark helps teachers deliver rapid, consistent marking with meaningful feedback for every student — in a fraction of the time. What once took a week, now takes one free period.
Reactive Resume
amruthpillaiA one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
Comments