Is io.fuse/mcp up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.fuse.io/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://mcp.fuse.io/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://mcp.fuse.io with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 50 tools: 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.
No change to its tools between 2026-09 and 2026-10.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.fuse/mcp |
|---|---|
| Endpoint | https://mcp.fuse.io/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt