Fuse Network
REMOTE · MCP.FUSE.IO · SCANNED SEP 22
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 50 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4371 tokens (~87/item across 50 items; 50 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "fuse_notification_delete_webhook" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 50 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Fuse Network MCP server?
Fuse Network is a hosted endpoint at https://mcp.fuse.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.fuse.io
claude mcp add --transport http io-fuse-mcp 'https://mcp.fuse.io/mcp'
{
"mcpServers": {
"io-fuse-mcp": {
"url": "https://mcp.fuse.io/mcp"
}
}
} {
"servers": {
"io-fuse-mcp": {
"type": "http",
"url": "https://mcp.fuse.io/mcp"
}
}
} [mcp_servers.io-fuse-mcp] url = "https://mcp.fuse.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-fuse-mcp": {
"type": "remote",
"url": "https://mcp.fuse.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-fuse-mcp --url 'https://mcp.fuse.io/mcp' --transport streamable-http
mcp_servers:
io-fuse-mcp:
url: "https://mcp.fuse.io/mcp" {
"McpServers": {
"io-fuse-mcp": {
"Transport": "http",
"Url": "https://mcp.fuse.io/mcp"
}
}
} assistant mcp add io-fuse-mcp -t streamable-http -u 'https://mcp.fuse.io/mcp'
{
"mcpServers": {
"io-fuse-mcp": {
"type": "http",
"url": "https://mcp.fuse.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 11 Sept 26 −1
- Stability: pass → 0.93 functional
- 27 Aug 26 +41
- Injection markers: unverified → pass ▲ security
- Stability: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 50 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- First check of Destructive annotations: 0 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Aug 26 −42
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 14 Aug 26 0
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 50 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.63 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.53 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://mcp.fuse.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.fuse.io | CN=YR2,O=Let's Encrypt,C=US | 25 Jul 2026 | 23 Oct 2026 | RSA 2048 | SHA256-RSA | 5ba0adfa7df09fceceacfd33ceeb2b620e9 |
| SANs: mcp.fuse.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.fuse.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| fuse.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.fuse.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.fuse.io/mcp | HTTPS enforced | 308 | https://mcp.fuse.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fuse_deploy_contract Deploy contract ~149
Signs and submits a contract-deployment transaction using the server's signer. Returns the transaction hash, and the deployed contract address when `waitForReceipt: true`.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | array | yes | Contract ABI. Required so constructor arguments can be encoded correctly. |
| args | array | – | Constructor arguments (defaults to []). |
| bytecode | string | yes | Contract creation bytecode as a 0x-prefixed hex string. |
| valueWei | string | – | Native FUSE to send with the deployment, in wei (payable constructors). |
| waitForReceipt | boolean | – | When true, the tool waits for the deployment to be mined and includes the deployed address in the response (default false). |
No output schema declared.
No examples provided.
fuse_explorer_query Fuse Explorer API query ~234
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action within the module — e.g. `balance`, `txlist`, `getabi`, `getLogs`, `eth_block_number`, `verify`. |
| body | object | – | JSON body for POST verify-* actions. |
| method | string | – | HTTP method (default GET). Use POST only for the five `contract/verify*` actions, which also accept a JSON body. |
| module | string | yes | Etherscan-style API module: `account`, `block`, `contract`, `logs`, `stats`, `token`, `transaction`. |
| params | object | – | Additional query parameters (e.g. `address`, `fromBlock`, `toBlock`, `topic0`). Omit `module`, `action`, and `apiKey` — they're injected automatically. |
No output schema declared.
No examples provided.
fuse_get_account_abstraction_info Get account abstraction info ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nonceKey | string | – | Optional 192-bit nonce key as a decimal or 0x-prefixed hex string (defaults to 0). |
| smartAccountAddress | string | yes | Smart-account (ERC-4337) address — counterfactual or deployed. |
No output schema declared.
No examples provided.
fuse_get_balance Get balance ~84
Returns the native FUSE balance for an address, or an ERC-20 token balance when `tokenAddress` is supplied.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EOA or contract address to query (0x-prefixed, EIP-55 or lowercase). |
| tokenAddress | string | – | Optional ERC-20 token address. Omit to fetch the native FUSE balance. |
No output schema declared.
No examples provided.
fuse_get_gas_price Get gas price ~37
Returns the current Fuse network gas price (in wei and gwei) along with EIP-1559 fee suggestions when available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fuse_get_receipt Get transaction receipt ~54
Fetches the receipt for a mined transaction (status, gasUsed, logs). Returns null if the transaction is pending or unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Transaction hash (0x-prefixed, 32 bytes). |
No output schema declared.
No examples provided.
fuse_get_signer_address Get signer address ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fuse_get_staked_tokens Get staked tokens ~63
Returns the active staking positions for a wallet — staked amount, USD value, earned rewards, and APR per position. Powered by the Fusebox SDK StakingModule.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Smart-wallet address whose active staking positions should be returned. |
No output schema declared.
No examples provided.
fuse_get_staking_options Get staking options ~45
Lists every staking option supported by Fuse — token, APR, TVL, expiry, and the matching unstake token. Powered by the Fusebox SDK StakingModule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fuse_get_token_metadata Get token metadata ~44
Reads name, symbol, decimals, and totalSupply for an ERC-20 token deployed on Fuse.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | ERC-20 token contract address. |
No output schema declared.
No examples provided.
fuse_get_token_price Get token price ~56
Returns the current USD price for an ERC-20 token tracked by Fusebox. Powered by the Fusebox SDK TradeModule.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Address of the ERC-20 token whose USD price should be returned. |
No output schema declared.
No examples provided.
fuse_get_token_price_change Get token 24h price change ~63
Returns the 24-hour percentage price change for an ERC-20 token tracked by Fusebox. Powered by the Fusebox SDK TradeModule.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Address of the ERC-20 token whose 24-hour price change should be returned. |
No output schema declared.
No examples provided.
fuse_get_token_price_history Get token price history ~78
Returns OHLC / interval price stats for an ERC-20 token over a week, month, or year. Powered by the Fusebox SDK TradeModule.
| Name | Type | Req | Description |
|---|---|---|---|
| timeFrame | string | yes | Granularity / range for the price series. |
| tokenAddress | string | yes | Address of the ERC-20 token to fetch price history for. |
No output schema declared.
No examples provided.
fuse_get_trade_quote Get trade quote ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount, expressed as a decimal string in the token's base units (wei for 18-decimal tokens). |
| exactIn | boolean | – | When true (default), `amount` is the sell amount. When false, `amount` is the desired buy amount. |
| inputToken | string | yes | Address of the token being sold. |
| outputToken | string | yes | Address of the token being bought. |
No output schema declared.
No examples provided.
fuse_get_transaction Get transaction ~43
Fetches a transaction by hash. Returns null if the transaction is not found.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Transaction hash (0x-prefixed, 32 bytes). |
No output schema declared.
No examples provided.
fuse_get_user_operations Get user operations ~65
Returns the ERC-4337 UserOperation history for a smart account on Fuse, indexed via the Fusebox GraphQL service. Powered by the Fusebox SDK GraphQLModule.
| Name | Type | Req | Description |
|---|---|---|---|
| sender | string | yes | Smart-account address (UserOperation `sender`) to fetch history for. |
No output schema declared.
No examples provided.
fuse_list_supported_tokens List supported tokens ~39
Returns the catalogue of ERC-20 tokens tracked by Fusebox (tradable, indexed, priced). Powered by the Fusebox SDK TradeModule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fuse_list_wallet_nfts List wallet NFTs ~58
Lists all NFTs (ERC-721 / ERC-1155 collectibles) owned by a wallet on Fuse. Powered by the Fusebox SDK BalancesModule.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Wallet address whose NFT holdings should be listed. |
No output schema declared.
No examples provided.
fuse_list_wallet_tokens List wallet tokens ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Wallet address whose ERC-20 token portfolio should be listed. |
No output schema declared.
No examples provided.
fuse_notification_add_addresses Add addresses to webhook ~63
Add one or more EVM addresses to a webhook's listening scope. Requires `FUSEBOX_SECRET_API_KEY`.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | EVM addresses to start monitoring for this webhook. |
| webhookId | string | yes | ID of the webhook to extend. |
No output schema declared.
No examples provided.
fuse_notification_create_webhook Create webhook ~110
Create a Fusebox Notification webhook for a project. Requires `FUSEBOX_SECRET_API_KEY` (Notification API endpoints authenticate with both apiKey and API-SECRET).
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Event filter. `ERC721` also covers ERC1155 events. `ALL` subscribes to every event type. |
| projectId | string | yes | Fuse Console project ID that owns the webhook. |
| webhookUrl | string | yes | HTTPS URL that Fusebox will POST event payloads to. |
No output schema declared.
No examples provided.
fuse_notification_delete_webhook Delete webhook ~52
Permanently delete a Fusebox Notification webhook. Destructive — the webhook stops receiving events. Requires `FUSEBOX_SECRET_API_KEY`.
| Name | Type | Req | Description |
|---|---|---|---|
| webhookId | string | yes | ID of the webhook to delete. |
No output schema declared.
No examples provided.
fuse_notification_get_webhook Get webhook by ID ~43
Retrieve details of a single Fusebox Notification webhook. Requires `FUSEBOX_SECRET_API_KEY`.
| Name | Type | Req | Description |
|---|---|---|---|
| webhookId | string | yes | Webhook ID to retrieve. |
No output schema declared.
No examples provided.
fuse_notification_list_addresses List webhook addresses ~47
List every EVM address monitored by a given webhook. Requires `FUSEBOX_SECRET_API_KEY`.
| Name | Type | Req | Description |
|---|---|---|---|
| webhookId | string | yes | Webhook ID whose monitored addresses should be listed. |
No output schema declared.
No examples provided.
fuse_notification_list_project_webhooks List project webhooks ~49
List every Fusebox Notification webhook configured for a given project. Requires `FUSEBOX_SECRET_API_KEY`.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Project ID whose webhooks should be listed. |
No output schema declared.
No examples provided.
fuse_notification_remove_addresses Remove addresses from webhook ~57
Remove EVM addresses from a webhook's listening scope. Requires `FUSEBOX_SECRET_API_KEY`.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | EVM addresses to stop monitoring. |
| webhookId | string | yes | ID of the webhook to modify. |
No output schema declared.
No examples provided.
fuse_notification_update_webhook Update webhook ~76
Update a Fusebox Notification webhook's URL or event type. Requires `FUSEBOX_SECRET_API_KEY`.
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Event filter (`ERC721` also covers ERC1155). |
| webhookId | string | yes | ID of the webhook to update. |
| webhookUrl | string | yes | New webhook URL. |
No output schema declared.
No examples provided.
fuse_read_contract Read contract ~100
Calls a view/pure function on a Fuse contract. ABI is auto-fetched from the verified Fuse explorer when not supplied.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | array | – | Optional ABI override. If omitted, the verified ABI is fetched from the Fuse explorer. |
| address | string | yes | Contract address. |
| args | array | – | Positional arguments for the function (defaults to []). |
| functionName | string | yes | Name of the view/pure function to call. |
No output schema declared.
No examples provided.
fuse_resolve_ens Resolve ENS name ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | ENS name to resolve (e.g. `vitalik.eth`). Plain addresses are returned unchanged. |
No output schema declared.
No examples provided.
fuse_send_erc20 Send ERC-20 ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer. Default unit is the token's display unit (decimals auto-detected); pass `unit: "base"` to send raw base units. |
| to | string | yes | Recipient address. |
| tokenAddress | string | yes | ERC-20 token contract address. |
| unit | string | – | – |
No output schema declared.
No examples provided.
fuse_send_native Send native FUSE ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of FUSE to send (default unit: FUSE — pass `unit: "wei"` for raw wei). |
| to | string | yes | Recipient address. |
| unit | string | – | `display` (default) treats `amount` as FUSE; `base` treats it as wei. |
No output schema declared.
No examples provided.
fuse_sign_message Sign message (EIP-191) ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | `utf8` (default) or `hex` for raw bytes. |
| message | string | yes | Message to sign. UTF-8 by default; pass `encoding: "hex"` for raw bytes (0x-prefixed). |
No output schema declared.
No examples provided.
fuse_sign_typed_data Sign typed data (EIP-712) ~116
Signs a structured EIP-712 payload with the server's signer. Returns the 65-byte signature as hex. No on-chain transaction is submitted.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | object | yes | EIP-712 domain separator object. |
| message | object | yes | Typed-data message conforming to `primaryType`. |
| primaryType | string | yes | Name of the primary type to hash. |
| types | object | yes | EIP-712 types map (exclude the `EIP712Domain` entry — it's derived from `domain`). |
No output schema declared.
No examples provided.
fuse_smart_approve_and_call Smart-account: approve + call ~126
Atomically approves a token and invokes a follow-up call on the spender from the configured smart wallet. Common DeFi pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Allowance amount in the token's display unit (or base if `unit: "base"`). |
| callData | string | yes | Encoded calldata to invoke on `spender` after approval (0x-prefixed hex). |
| spender | string | yes | Contract that will receive the subsequent call. |
| tokenAddress | string | yes | ERC-20 token contract address to approve. |
| unit | string | – | – |
No output schema declared.
No examples provided.
fuse_smart_approve_nft Smart-account: approve NFT ~90
Submits an ERC-4337 UserOperation calling `approve(spender, tokenId)` on an NFT contract from the configured smart wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| nftContractAddress | string | yes | ERC-721 / ERC-1155 contract address. |
| spender | string | yes | Address being granted approval for the token ID. |
| tokenId | string | yes | NFT token ID (decimal or hex). |
No output schema declared.
No examples provided.
fuse_smart_approve_token Smart-account: approve token ~113
Submits an ERC-4337 UserOperation calling `ERC20.approve(spender, amount)` from the configured smart wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Allowance amount. Default unit is the token's display unit; pass `unit: "base"` for raw base units. Use `"max"` to approve the uint256 maximum. |
| spender | string | yes | Address being granted spending allowance. |
| tokenAddress | string | yes | ERC-20 token contract address. |
| unit | string | – | – |
No output schema declared.
No examples provided.
fuse_smart_call_contract Smart-account: call contract ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Encoded calldata (0x-prefixed hex). |
| to | string | yes | Target contract address. |
| valueWei | string | – | Native FUSE to send with the call, in wei (default `0`). |
No output schema declared.
No examples provided.
fuse_smart_execute_batch Smart-account: execute batch ~61
Submits a single ERC-4337 UserOperation that executes a sequence of contract calls atomically. Failed sub-calls revert the whole batch.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | yes | Ordered list of contract calls to execute atomically as a single UserOp. |
No output schema declared.
No examples provided.
fuse_smart_get_info Get smart-wallet info ~40
Returns the ERC-4337 smart-wallet address derived from the configured signer, plus whether the Fuse paymaster (gasless mode) is enabled.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fuse_smart_stake_token Smart-account: stake token ~87
Submits an ERC-4337 UserOperation that stakes a token using Fuse's staking module. List options first with `fuse_get_staking_options`.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Token to stake (must match a `fuse_get_staking_options` entry). |
| tokenAmount | string | yes | Amount in base units (wei for 18-decimal tokens). |
No output schema declared.
No examples provided.
fuse_smart_swap_tokens Smart-account: swap tokens ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exactIn | boolean | – | `true` (default) treats `inputAmount` as sell amount; `false` treats it as buy amount. |
| inputAmount | string | yes | Amount in base units (wei for 18-decimal tokens). |
| inputToken | string | yes | Address of the token being sold. |
| outputToken | string | yes | Address of the token being bought. |
No output schema declared.
No examples provided.
fuse_smart_transfer_nft Smart-account: transfer NFT ~92
Submits an ERC-4337 UserOperation transferring an NFT (ERC-721 / ERC-1155) from the configured smart wallet to a recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| nftContractAddress | string | yes | ERC-721 / ERC-1155 contract address. |
| to | string | yes | Recipient address. |
| tokenId | string | yes | NFT token ID (decimal or 0x-prefixed hex string). |
No output schema declared.
No examples provided.
fuse_smart_transfer_token Smart-account: transfer token ~130
Submits an ERC-4337 UserOperation transferring a token (native FUSE or ERC-20) from the configured smart wallet. Gasless when `FUSE_USE_PAYMASTER=true`.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer. Default unit is the token's display unit; pass `unit: "base"` for raw base units. |
| to | string | yes | Recipient address. |
| tokenAddress | string | yes | Token contract address. Use the native-token sentinel `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` for FUSE. |
| unit | string | – | – |
No output schema declared.
No examples provided.
fuse_smart_unstake_token Smart-account: unstake token ~92
Submits an ERC-4337 UserOperation that unstakes a token via Fuse's staking module.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Original staking-token address. |
| tokenAmount | string | yes | Amount to unstake, in base units. |
| unstakeTokenAddress | string | yes | Receipt token address paired with the stake (`unStakeTokenAddress` from `fuse_get_staking_options`). |
No output schema declared.
No examples provided.
fuse_smart_wallet_authenticate Authenticate smart wallet ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Signed message hash (EIP-191). |
| ownerAddress | string | yes | EOA address that signed the hash (the smart wallet's owner). |
| signature | string | yes | EIP-191 signature produced by the EOA owner. |
| smartWalletAddress | string | yes | Deployed smart contract wallet address. |
No output schema declared.
No examples provided.
fuse_smart_wallet_get_actions Get smart wallet actions ~109
List the paginated action history (transfers, contract calls) of an authenticated smart wallet. The JWT comes from `fuse_smart_wallet_authenticate`.
| Name | Type | Req | Description |
|---|---|---|---|
| jwt | string | yes | Bearer JWT issued by `fuse_smart_wallet_authenticate`. |
| limit | integer | – | Items per page (default 10). |
| page | integer | – | Pagination page (default 1). |
| tokenAddress | string | – | Optional ERC-20 token address to filter actions by. |
No output schema declared.
No examples provided.
fuse_trade_indicative_price Get indicative trade price ~270
Returns an indicative price + route for a swap on Fuse (0x-style response). One of `sellAmount` / `buyAmount` must be provided.
| Name | Type | Req | Description |
|---|---|---|---|
| buyAmount | string | – | Desired buy amount in base units (mutually exclusive with `sellAmount`). |
| buyToken | string | yes | ERC-20 contract address of the token to buy. |
| buyTokenPercentageFee | string | – | – |
| enableSlippageProtection | boolean | – | – |
| excludedSources | string | – | Comma-separated liquidity sources to exclude. |
| feeRecipient | string | – | – |
| feeRecipientTradeSurplus | string | – | – |
| gasPrice | string | – | Gas price override in wei. |
| includedSources | string | – | Comma-separated liquidity sources to include. |
| priceImpactProtectionPercentage | string | – | – |
| sellAmount | string | – | Sell amount in base units (mutually exclusive with `buyAmount`). |
| sellToken | string | yes | ERC-20 contract address of the token to sell. |
| skipValidation | boolean | – | – |
| slippagePercentage | string | – | Max slippage as a decimal string (e.g. `0.01` = 1%). |
| takerAddress | string | – | Address of the trader (for validation). |
No output schema declared.
No examples provided.
fuse_trade_liquidity_sources List liquidity sources ~33
Returns the liquidity sources currently enabled for Fuse-chain trades (e.g. voltage.finance, sub-pools).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fuse_trade_price_change_over_duration Get token price change over duration ~71
Returns a token's price change over a custom day-count window (`{ priceChange, currentPrice, previousPrice }`).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | yes | Number of days to look back when computing the price change. |
| tokenAddress | string | yes | ERC-20 contract address of the token. |
No output schema declared.
No examples provided.
fuse_write_contract Write contract ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | array | – | Optional ABI override. If omitted, the verified ABI is fetched from the Fuse explorer. |
| address | string | yes | Contract address. |
| args | array | – | Positional arguments (defaults to []). |
| functionName | string | yes | State-mutating function to call. |
| valueWei | string | – | Native FUSE value to send with the call, in wei (for payable functions). |
No output schema declared.
No examples provided.
What is the Fuse Network MCP server?
Fuse Network is an MCP server listed in the public MCP registry as io.fuse/mcp. MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions. This page covers its hosted endpoint (https://mcp.fuse.io/mcp).
Is the Fuse Network MCP server safe to use?
Fuse Network scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fuse Network MCP server expose?
Fuse Network exposes 50 tools: fuse_get_balance, fuse_get_transaction, fuse_get_receipt, fuse_read_contract, fuse_get_token_metadata, and 45 more. Their descriptions and schemas cost roughly 4,371 tokens of context every time the server is loaded.
Does the Fuse Network MCP server require authentication?
No. We connected to Fuse Network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fuse Network MCP server still maintained?
Fuse Network is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.