Remote MCP · Endpoint

Fuse Network MCP server

No. Fuse Network answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.fuse.io/mcp

The last check completed an MCP handshake.

Registry name
io.fuse/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
40 ms
Tools exposed
50 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Listing
From the official MCP registry (active).
Recent checks of Fuse Network
CheckedResultHandshake
1 hour agoHandshake completed40 ms
2 days agoHandshake completed36 ms
4 days agoHandshake completed97 ms
5 days agoHandshake completed33 ms
7 days agoHandshake completed47 ms
8 days agoHandshake completed41 ms
9 days agoHandshake completed35 ms
12 days agoHandshake completed215 ms
13 days agoHandshake completed50 ms
15 days agoHandshake completed60 ms
16 days agoHandshake completed37 ms
18 days agoHandshake completed42 ms
19 days agoHandshake completed36 ms
20 days agoHandshake completed45 ms
20 days agoHandshake completed933 ms
21 days agoHandshake completed40 ms
22 days agoHandshake completed42 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Fuse Network and makes no claim about it beyond what these checks measured.