Remote MCP · Endpoint

AgentData - Executable Liquidity / Exit-Cost MCP server

No. AgentData - Executable Liquidity / Exit-Cost answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agentdata-liquidity-exit-cost.onrender.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.phenicea/agentdata-liquidity-exit-cost
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
170 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Size-aware exit cost, depeg risk & liquidity fragility for a Base token (x402, testnet).
Listing
From the official MCP registry (active).
Recent checks of AgentData - Executable Liquidity / Exit-Cost
CheckedResultHandshake
1 hour agoHandshake completed170 ms
2 days agoHandshake completed305 ms
4 days agoHandshake completed270 ms
5 days agoHandshake completed115 ms
7 days agoHandshake completed297 ms
8 days agoHandshake completed123 ms
9 days agoHandshake completed265 ms
12 days agoHandshake completed136 ms
13 days agoHandshake completed138 ms
15 days agoHandshake completed298 ms
17 days agoHandshake completed132 ms
18 days agoHandshake completed129 ms
19 days agoHandshake completed138 ms
20 days agoHandshake completed102 ms
20 days agoHandshake completed268 ms
21 days agoHandshake completed120 ms
23 days agoHandshake completed127 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 AgentData - Executable Liquidity / Exit-Cost and makes no claim about it beyond what these checks measured.