Remote MCP · Endpoint

Liqwall market data MCP server

No. Liqwall market data answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://liqwall.com/mcp

The last check completed an MCP handshake.

Registry name
com.liqwall/market-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
530 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Crypto liquidation maps, liquidations, funding, open interest: 4 tools without a key, 6 with one.
Listing
From the official MCP registry (active).
Recent checks of Liqwall market data
CheckedResultHandshake
7 hours agoHandshake completed530 ms
13 hours agoHandshake completed569 ms
2 days agoHandshake completed491 ms
4 days agoHandshake completed502 ms
7 days agoHandshake completed504 ms
9 days agoHandshake completed494 ms
11 days agoHandshake completed503 ms
14 days agoHandshake completed500 ms
16 days agoHandshake completed505 ms
18 days agoHandshake completed494 ms
20 days agoHandshake completed584 ms
21 days agoCredentials required—
23 days agoCredentials required—

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

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