Home / MCP registry index / io.fuse/mcp

Fuse Network

io.fuse/mcp in the official MCP registry. Endpoint https://mcp.fuse.io/mcp.

The registry describes it as: MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http mcp https://mcp.fuse.io/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.fuse.io/mcp"
    }
  }
}

code --add-mcp '{"name":"mcp","type":"http","url":"https://mcp.fuse.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

fuse_get_balance fuse_get_transaction fuse_get_receipt fuse_read_contract fuse_get_token_metadata fuse_get_gas_price fuse_resolve_ens fuse_get_account_abstraction_info fuse_list_wallet_tokens fuse_list_wallet_nfts fuse_get_staking_options fuse_get_staked_tokens fuse_get_token_price fuse_get_token_price_change fuse_get_token_price_history fuse_list_supported_tokens fuse_get_trade_quote fuse_get_user_operations fuse_notification_create_webhook fuse_notification_get_webhook fuse_notification_list_project_webhooks fuse_notification_update_webhook fuse_notification_delete_webhook fuse_notification_add_addresses fuse_notification_remove_addresses fuse_notification_list_addresses fuse_smart_wallet_authenticate fuse_smart_wallet_get_actions fuse_trade_indicative_price fuse_trade_liquidity_sources fuse_trade_price_change_over_duration fuse_explorer_query fuse_get_signer_address fuse_send_native fuse_send_erc20 fuse_write_contract fuse_deploy_contract fuse_sign_message fuse_sign_typed_data fuse_smart_get_info fuse_smart_transfer_token fuse_smart_transfer_nft fuse_smart_approve_token fuse_smart_approve_nft fuse_smart_approve_and_call fuse_smart_call_contract fuse_smart_execute_batch fuse_smart_swap_tokens fuse_smart_stake_token fuse_smart_unstake_token

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-fuse-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-fuse-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers