Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fuse Network

REMOTE · MCP.FUSE.IO

MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.

Available components

0 this week 80 Trust /100

Last scanned (15 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
Transport & Reachability100
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Sept 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
Diagnostics

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 21 Nov 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 23 Sept 2026 22 Dec 2026 RSA 2048 SHA256-RSA 60653e626bc9a199676ffa6de4ad8dd6c92
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. DS published 38690 8 Verified
fuse.io. No DS 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
MCP tools · 50 exposed · ~4,371 tokens

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 →

Tool Tokens
fuse_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`.

NameTypeReqDescription
abiarrayyesContract ABI. Required so constructor arguments can be encoded correctly.
argsarray–Constructor arguments (defaults to []).
bytecodestringyesContract creation bytecode as a 0x-prefixed hex string.
valueWeistring–Native FUSE to send with the deployment, in wei (payable constructors).
waitForReceiptboolean–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 ~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.

NameTypeReqDescription
actionstringyesAction within the module — e.g. `balance`, `txlist`, `getabi`, `getLogs`, `eth_block_number`, `verify`.
bodyobject–JSON body for POST verify-* actions.
methodstring–HTTP method (default GET). Use POST only for the five `contract/verify*` actions, which also accept a JSON body.
modulestringyesEtherscan-style API module: `account`, `block`, `contract`, `logs`, `stats`, `token`, `transaction`.
paramsobject–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 ~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.

NameTypeReqDescription
nonceKeystring–Optional 192-bit nonce key as a decimal or 0x-prefixed hex string (defaults to 0).
smartAccountAddressstringyesSmart-account (ERC-4337) address — counterfactual or deployed.

No output schema declared.

No examples provided.

fuse_get_balance ~84

Returns the native FUSE balance for an address, or an ERC-20 token balance when `tokenAddress` is supplied.

NameTypeReqDescription
addressstringyesEOA or contract address to query (0x-prefixed, EIP-55 or lowercase).
tokenAddressstring–Optional ERC-20 token address. Omit to fetch the native FUSE balance.

No output schema declared.

No examples provided.

fuse_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 ~54

Fetches the receipt for a mined transaction (status, gasUsed, logs). Returns null if the transaction is pending or unknown.

NameTypeReqDescription
hashstringyesTransaction hash (0x-prefixed, 32 bytes).

No output schema declared.

No examples provided.

fuse_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 ~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.

NameTypeReqDescription
walletAddressstringyesSmart-wallet address whose active staking positions should be returned.

No output schema declared.

No examples provided.

fuse_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 ~44

Reads name, symbol, decimals, and totalSupply for an ERC-20 token deployed on Fuse.

NameTypeReqDescription
tokenAddressstringyesERC-20 token contract address.

No output schema declared.

No examples provided.

fuse_get_token_price ~56

Returns the current USD price for an ERC-20 token tracked by Fusebox. Powered by the Fusebox SDK TradeModule.

NameTypeReqDescription
tokenAddressstringyesAddress of the ERC-20 token whose USD price should be returned.

No output schema declared.

No examples provided.

fuse_get_token_price_change ~63

Returns the 24-hour percentage price change for an ERC-20 token tracked by Fusebox. Powered by the Fusebox SDK TradeModule.

NameTypeReqDescription
tokenAddressstringyesAddress 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 ~78

Returns OHLC / interval price stats for an ERC-20 token over a week, month, or year. Powered by the Fusebox SDK TradeModule.

NameTypeReqDescription
timeFramestringyesGranularity / range for the price series.
tokenAddressstringyesAddress of the ERC-20 token to fetch price history for.

No output schema declared.

No examples provided.

fuse_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.

NameTypeReqDescription
amountstringyesAmount, expressed as a decimal string in the token's base units (wei for 18-decimal tokens).
exactInboolean–When true (default), `amount` is the sell amount. When false, `amount` is the desired buy amount.
inputTokenstringyesAddress of the token being sold.
outputTokenstringyesAddress of the token being bought.

No output schema declared.

No examples provided.

fuse_get_transaction ~43

Fetches a transaction by hash. Returns null if the transaction is not found.

NameTypeReqDescription
hashstringyesTransaction hash (0x-prefixed, 32 bytes).

No output schema declared.

No examples provided.

fuse_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.

NameTypeReqDescription
senderstringyesSmart-account address (UserOperation `sender`) to fetch history for.

No output schema declared.

No examples provided.

fuse_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 ~58

Lists all NFTs (ERC-721 / ERC-1155 collectibles) owned by a wallet on Fuse. Powered by the Fusebox SDK BalancesModule.

NameTypeReqDescription
walletAddressstringyesWallet address whose NFT holdings should be listed.

No output schema declared.

No examples provided.

fuse_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.

NameTypeReqDescription
walletAddressstringyesWallet address whose ERC-20 token portfolio should be listed.

No output schema declared.

No examples provided.

fuse_notification_add_addresses ~63

Add one or more EVM addresses to a webhook's listening scope. Requires `FUSEBOX_SECRET_API_KEY`.

NameTypeReqDescription
addressesarrayyesEVM addresses to start monitoring for this webhook.
webhookIdstringyesID of the webhook to extend.

No output schema declared.

No examples provided.

fuse_notification_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).

NameTypeReqDescription
eventTypestringyesEvent filter. `ERC721` also covers ERC1155 events. `ALL` subscribes to every event type.
projectIdstringyesFuse Console project ID that owns the webhook.
webhookUrlstringyesHTTPS URL that Fusebox will POST event payloads to.

No output schema declared.

No examples provided.

fuse_notification_delete_webhook ~52

Permanently delete a Fusebox Notification webhook. Destructive — the webhook stops receiving events. Requires `FUSEBOX_SECRET_API_KEY`.

NameTypeReqDescription
webhookIdstringyesID of the webhook to delete.

No output schema declared.

No examples provided.

fuse_notification_get_webhook ~43

Retrieve details of a single Fusebox Notification webhook. Requires `FUSEBOX_SECRET_API_KEY`.

NameTypeReqDescription
webhookIdstringyesWebhook ID to retrieve.

No output schema declared.

No examples provided.

fuse_notification_list_addresses ~47

List every EVM address monitored by a given webhook. Requires `FUSEBOX_SECRET_API_KEY`.

NameTypeReqDescription
webhookIdstringyesWebhook ID whose monitored addresses should be listed.

No output schema declared.

No examples provided.

fuse_notification_list_project_webhooks ~49

List every Fusebox Notification webhook configured for a given project. Requires `FUSEBOX_SECRET_API_KEY`.

NameTypeReqDescription
projectIdstringyesProject ID whose webhooks should be listed.

No output schema declared.

No examples provided.

fuse_notification_remove_addresses ~57

Remove EVM addresses from a webhook's listening scope. Requires `FUSEBOX_SECRET_API_KEY`.

NameTypeReqDescription
addressesarrayyesEVM addresses to stop monitoring.
webhookIdstringyesID of the webhook to modify.

No output schema declared.

No examples provided.

fuse_notification_update_webhook ~76

Update a Fusebox Notification webhook's URL or event type. Requires `FUSEBOX_SECRET_API_KEY`.

NameTypeReqDescription
eventTypestringyesEvent filter (`ERC721` also covers ERC1155).
webhookIdstringyesID of the webhook to update.
webhookUrlstringyesNew webhook URL.

No output schema declared.

No examples provided.

fuse_read_contract ~100

Calls a view/pure function on a Fuse contract. ABI is auto-fetched from the verified Fuse explorer when not supplied.

NameTypeReqDescription
abiarray–Optional ABI override. If omitted, the verified ABI is fetched from the Fuse explorer.
addressstringyesContract address.
argsarray–Positional arguments for the function (defaults to []).
functionNamestringyesName of the view/pure function to call.

No output schema declared.

No examples provided.

fuse_resolve_ens ~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.

NameTypeReqDescription
namestringyesENS name to resolve (e.g. `vitalik.eth`). Plain addresses are returned unchanged.

No output schema declared.

No examples provided.

fuse_send_erc20 ~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.

NameTypeReqDescription
amountstringyesAmount to transfer. Default unit is the token's display unit (decimals auto-detected); pass `unit: "base"` to send raw base units.
tostringyesRecipient address.
tokenAddressstringyesERC-20 token contract address.
unitstring––

No output schema declared.

No examples provided.

fuse_send_native ~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.

NameTypeReqDescription
amountstringyesAmount of FUSE to send (default unit: FUSE — pass `unit: "wei"` for raw wei).
tostringyesRecipient address.
unitstring–`display` (default) treats `amount` as FUSE; `base` treats it as wei.

No output schema declared.

No examples provided.

fuse_sign_message ~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.

NameTypeReqDescription
encodingstring–`utf8` (default) or `hex` for raw bytes.
messagestringyesMessage 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 ~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.

NameTypeReqDescription
domainobjectyesEIP-712 domain separator object.
messageobjectyesTyped-data message conforming to `primaryType`.
primaryTypestringyesName of the primary type to hash.
typesobjectyesEIP-712 types map (exclude the `EIP712Domain` entry — it's derived from `domain`).

No output schema declared.

No examples provided.

fuse_smart_approve_and_call ~126

Atomically approves a token and invokes a follow-up call on the spender from the configured smart wallet. Common DeFi pattern.

NameTypeReqDescription
amountstringyesAllowance amount in the token's display unit (or base if `unit: "base"`).
callDatastringyesEncoded calldata to invoke on `spender` after approval (0x-prefixed hex).
spenderstringyesContract that will receive the subsequent call.
tokenAddressstringyesERC-20 token contract address to approve.
unitstring––

No output schema declared.

No examples provided.

fuse_smart_approve_nft ~90

Submits an ERC-4337 UserOperation calling `approve(spender, tokenId)` on an NFT contract from the configured smart wallet.

NameTypeReqDescription
nftContractAddressstringyesERC-721 / ERC-1155 contract address.
spenderstringyesAddress being granted approval for the token ID.
tokenIdstringyesNFT token ID (decimal or hex).

No output schema declared.

No examples provided.

fuse_smart_approve_token ~113

Submits an ERC-4337 UserOperation calling `ERC20.approve(spender, amount)` from the configured smart wallet.

NameTypeReqDescription
amountstringyesAllowance amount. Default unit is the token's display unit; pass `unit: "base"` for raw base units. Use `"max"` to approve the uint256 maximum.
spenderstringyesAddress being granted spending allowance.
tokenAddressstringyesERC-20 token contract address.
unitstring––

No output schema declared.

No examples provided.

fuse_smart_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.

NameTypeReqDescription
datastringyesEncoded calldata (0x-prefixed hex).
tostringyesTarget contract address.
valueWeistring–Native FUSE to send with the call, in wei (default `0`).

No output schema declared.

No examples provided.

fuse_smart_execute_batch ~61

Submits a single ERC-4337 UserOperation that executes a sequence of contract calls atomically. Failed sub-calls revert the whole batch.

NameTypeReqDescription
callsarrayyesOrdered list of contract calls to execute atomically as a single UserOp.

No output schema declared.

No examples provided.

fuse_smart_get_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 ~87

Submits an ERC-4337 UserOperation that stakes a token using Fuse's staking module. List options first with `fuse_get_staking_options`.

NameTypeReqDescription
tokenAddressstringyesToken to stake (must match a `fuse_get_staking_options` entry).
tokenAmountstringyesAmount in base units (wei for 18-decimal tokens).

No output schema declared.

No examples provided.

fuse_smart_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.

NameTypeReqDescription
exactInboolean–`true` (default) treats `inputAmount` as sell amount; `false` treats it as buy amount.
inputAmountstringyesAmount in base units (wei for 18-decimal tokens).
inputTokenstringyesAddress of the token being sold.
outputTokenstringyesAddress of the token being bought.

No output schema declared.

No examples provided.

fuse_smart_transfer_nft ~92

Submits an ERC-4337 UserOperation transferring an NFT (ERC-721 / ERC-1155) from the configured smart wallet to a recipient.

NameTypeReqDescription
nftContractAddressstringyesERC-721 / ERC-1155 contract address.
tostringyesRecipient address.
tokenIdstringyesNFT token ID (decimal or 0x-prefixed hex string).

No output schema declared.

No examples provided.

fuse_smart_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`.

NameTypeReqDescription
amountstringyesAmount to transfer. Default unit is the token's display unit; pass `unit: "base"` for raw base units.
tostringyesRecipient address.
tokenAddressstringyesToken contract address. Use the native-token sentinel `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` for FUSE.
unitstring––

No output schema declared.

No examples provided.

fuse_smart_unstake_token ~92

Submits an ERC-4337 UserOperation that unstakes a token via Fuse's staking module.

NameTypeReqDescription
tokenAddressstringyesOriginal staking-token address.
tokenAmountstringyesAmount to unstake, in base units.
unstakeTokenAddressstringyesReceipt token address paired with the stake (`unStakeTokenAddress` from `fuse_get_staking_options`).

No output schema declared.

No examples provided.

fuse_smart_wallet_authenticate ~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.

NameTypeReqDescription
hashstringyesSigned message hash (EIP-191).
ownerAddressstringyesEOA address that signed the hash (the smart wallet's owner).
signaturestringyesEIP-191 signature produced by the EOA owner.
smartWalletAddressstringyesDeployed smart contract wallet address.

No output schema declared.

No examples provided.

fuse_smart_wallet_get_actions ~109

List the paginated action history (transfers, contract calls) of an authenticated smart wallet. The JWT comes from `fuse_smart_wallet_authenticate`.

NameTypeReqDescription
jwtstringyesBearer JWT issued by `fuse_smart_wallet_authenticate`.
limitinteger–Items per page (default 10).
pageinteger–Pagination page (default 1).
tokenAddressstring–Optional ERC-20 token address to filter actions by.

No output schema declared.

No examples provided.

fuse_trade_indicative_price ~270

Returns an indicative price + route for a swap on Fuse (0x-style response). One of `sellAmount` / `buyAmount` must be provided.

NameTypeReqDescription
buyAmountstring–Desired buy amount in base units (mutually exclusive with `sellAmount`).
buyTokenstringyesERC-20 contract address of the token to buy.
buyTokenPercentageFeestring––
enableSlippageProtectionboolean––
excludedSourcesstring–Comma-separated liquidity sources to exclude.
feeRecipientstring––
feeRecipientTradeSurplusstring––
gasPricestring–Gas price override in wei.
includedSourcesstring–Comma-separated liquidity sources to include.
priceImpactProtectionPercentagestring––
sellAmountstring–Sell amount in base units (mutually exclusive with `buyAmount`).
sellTokenstringyesERC-20 contract address of the token to sell.
skipValidationboolean––
slippagePercentagestring–Max slippage as a decimal string (e.g. `0.01` = 1%).
takerAddressstring–Address of the trader (for validation).

No output schema declared.

No examples provided.

fuse_trade_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 ~71

Returns a token's price change over a custom day-count window (`{ priceChange, currentPrice, previousPrice }`).

NameTypeReqDescription
daysintegeryesNumber of days to look back when computing the price change.
tokenAddressstringyesERC-20 contract address of the token.

No output schema declared.

No examples provided.

fuse_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.

NameTypeReqDescription
abiarray–Optional ABI override. If omitted, the verified ABI is fetched from the Fuse explorer.
addressstringyesContract address.
argsarray–Positional arguments (defaults to []).
functionNamestringyesState-mutating function to call.
valueWeistring–Native FUSE value to send with the call, in wei (for payable functions).

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http io-fuse-mcp 'https://mcp.fuse.io/mcp'
Common questions

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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Fuse Network MCP server?

VerifyMCP ran 12 checks on Fuse Network, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Fuse Network: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.