Remote MCP · Endpoint

Floatout MCP server

No. Floatout answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://floatout.xyz/api/mcp

The last check completed an MCP handshake.

Registry name
xyz.floatout/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.08 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Launch a branded Hyperliquid perps and prediction market DEX. Read plans, guides and fee research.
Listing
From the official MCP registry (active).
Recent checks of Floatout
CheckedResultHandshake
18 minutes agoHandshake completed1.08 s
9 days agoHandshake completed935 ms
9 days agoHandshake completed523 ms
11 days agoHandshake completed590 ms
12 days agoHandshake completed1.20 s
13 days agoHandshake completed572 ms
14 days agoHandshake completed507 ms
14 days agoHandshake completed558 ms
16 days agoHandshake completed426 ms
19 days agoHandshake completed1.03 s
21 days agoHandshake completed892 ms
24 days agoHandshake completed1.49 s
26 days agoHandshake completed651 ms
28 days agoHandshake completed545 ms

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

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 Floatout and makes no claim about it beyond what these checks measured.