Remote MCP · Endpoint

io.github.ironflowsh/mcp MCP server

No. io.github.ironflowsh/mcp answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.ironflow.sh/mcp

The last check completed an MCP handshake.

Registry name
io.github.ironflowsh/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
519 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Read-only Hyperliquid data for AI agents: fills, candles, funding, liquidations, wallet analytics.
Repository
https://github.com/ironflowsh/mcp
Listing
From the official MCP registry (active).
Recent checks of io.github.ironflowsh/mcp
CheckedResultHandshake
2 hours agoHandshake completed519 ms
2 days agoHandshake completed503 ms
4 days agoHandshake completed475 ms
5 days agoHandshake completed461 ms
7 days agoHandshake completed486 ms
8 days agoHandshake completed376 ms
9 days agoHandshake completed469 ms
12 days agoHandshake completed477 ms
13 days agoHandshake completed466 ms
15 days agoHandshake completed463 ms
17 days agoHandshake completed466 ms
18 days agoHandshake completed439 ms
19 days agoHandshake completed460 ms
20 days agoHandshake completed464 ms
20 days agoHandshake completed473 ms
21 days agoHandshake completed467 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.ironflowsh/mcp and makes no claim about it beyond what these checks measured.