Remote MCP · Endpoint

Hyperliquid MCP server

No. Hyperliquid answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://gateway.pipeworx.io/hyperliquid/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/hyperliquid
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.01 s
Tools exposed
54 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hyperliquid MCP — read-only market data from Hyperliquid's public info API.
Listing
From the official MCP registry (active).
Recent checks of Hyperliquid
CheckedResultHandshake
6 hours agoHandshake completed1.01 s
3 days agoHandshake completed456 ms
12 days agoHandshake completed308 ms
13 days agoHandshake completed173 ms
14 days agoHandshake completed172 ms
15 days agoHandshake completed282 ms
16 days agoHandshake completed121 ms
17 days agoHandshake completed80 ms
18 days agoHandshake completed1.17 s
20 days agoHandshake completed1.19 s
23 days agoHandshake completed91 ms
25 days agoHandshake completed546 ms
27 days agoHandshake completed62 ms

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

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