Fuse Network
MCP server · mcp.fuse.io · found in a public registry · checked since 2026-10-17
Live, handshake completed · latest check
Provides Fuse Network balances, tokens, staking, DeFi data, swaps and transactions.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/3). What this means
Placed in Wallet balances and flows: Balances, holdings, history and profiles of wallet addresses, exchange flows and whale tracking.
GET https://mcp.fuse.io/mcpThe name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
3 passed, 0 failed, 27 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-20 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-20 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-20 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
fuse_deploy_contractfuse_explorer_queryfuse_get_account_abstraction_infofuse_get_balancefuse_get_gas_pricefuse_get_receiptfuse_get_signer_addressfuse_get_staked_tokensfuse_get_staking_optionsfuse_get_token_metadatafuse_get_token_pricefuse_get_token_price_changefuse_get_token_price_historyfuse_get_trade_quotefuse_get_transactionfuse_get_user_operationsfuse_list_supported_tokensfuse_list_wallet_nftsfuse_list_wallet_tokensfuse_notification_add_addressesfuse_notification_create_webhookfuse_notification_delete_webhookfuse_notification_get_webhookfuse_notification_list_addressesfuse_notification_list_project_webhooksfuse_notification_remove_addressesfuse_notification_update_webhookfuse_read_contractfuse_resolve_ensfuse_send_erc20fuse_send_nativefuse_sign_messagefuse_sign_typed_datafuse_smart_approve_and_callfuse_smart_approve_nftfuse_smart_approve_tokenfuse_smart_call_contractfuse_smart_execute_batchfuse_smart_get_infofuse_smart_stake_token+10
- Tools
- 50
- This list since
- 2026-10-20
- First listed to us
- 2026-10-20
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/1); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Financial and economic data / Crypto and on-chain data / Wallet balances and flows (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/5): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, MCP endpoint answered HTTP 200 | 144 ms |
cloudflare:EWR |
Live, MCP endpoint answered HTTP 400 | 101 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 400 | 210 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for 3 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_1b65b8063d6f7ad2