Remote MCP · Endpoint
EchoLedger MCP server
No. EchoLedger answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.echoledger.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.icmoore/echoledger-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 406 ms
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Live LP analytics — Uniswap V2/V3, Balancer, Curve stableswap: PnL, health, slippage, depeg risk.
- Website
- https://echoledger.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 406 ms |
| 2 days ago | Handshake completed | 779 ms |
| 4 days ago | Handshake completed | 153 ms |
| 5 days ago | Handshake completed | 135 ms |
| 7 days ago | Handshake completed | 148 ms |
| 8 days ago | Handshake completed | 461 ms |
| 9 days ago | Handshake completed | 115 ms |
| 12 days ago | Handshake completed | 119 ms |
| 13 days ago | Handshake completed | 137 ms |
| 15 days ago | Handshake completed | 121 ms |
| 17 days ago | Handshake completed | 208 ms |
| 18 days ago | Handshake completed | 155 ms |
| 19 days ago | Handshake completed | 143 ms |
| 20 days ago | Handshake completed | 138 ms |
| 20 days ago | Handshake completed | 113 ms |
| 21 days ago | Handshake completed | 115 ms |
| 23 days ago | Handshake completed | 137 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 EchoLedger and makes no claim about it beyond what these checks measured.