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
- 173 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Size-aware exit cost, depeg risk & liquidity fragility for a Base token (x402, testnet).
- Repository
- https://github.com/phenicea/agentdata
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 173 ms |
| 1 day ago | Handshake completed | 171 ms |
| 2 days ago | Handshake completed | 144 ms |
| 3 days ago | Handshake completed | 229 ms |
| 4 days ago | Handshake completed | 138 ms |
| 5 days ago | Handshake completed | 122 ms |
| 6 days ago | Handshake completed | 142 ms |
| 9 days ago | Handshake completed | 122 ms |
| 11 days ago | Handshake completed | 200 ms |
| 14 days ago | Handshake completed | 264 ms |
| 16 days ago | Handshake completed | 186 ms |
| 18 days ago | Handshake completed | 344 ms |
| 20 days ago | Handshake completed | 170 ms |
| 22 days ago | Handshake completed | 305 ms |
| 24 days ago | Handshake completed | 270 ms |
| 26 days ago | Handshake completed | 115 ms |
| 28 days ago | Handshake completed | 297 ms |
| 29 days ago | Handshake completed | 123 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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.