Should my agent depend on the MCP server io.fuse/mcp?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Fuse Network

io.fuse/mcp

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

— the operator's own registry description reported

Publisher io.fuse · first seen 2026-08-12 · endpoint https://mcp.fuse.io/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.478 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency71 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools50

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_28b70cd9a28cddb2909c056c · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

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

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	50/50	✓
has a description	50/50	✓
description is substantive	50/50	✓
parameters are typed	50/50	✓
parameters are described	45/50	45/50

50 of 50 tools graded · 50 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.1.0

server version fuse-mcp-server

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-14	outcome	ok_tools (was http_error)
2026-08-12	outcome	first probe: http_error

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:52Z	ok_tools	200	71	2025-06-18
2026-08-12T05:34:06Z	http_error	503	28

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.fuse/mcp.svg)](https://robinsaige.com/s/io.fuse/mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview