Remote MCP · Endpoint
ai.dataecho/mcp MCP server
No. ai.dataecho/mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://dataecho.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.dataecho/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 419 ms
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory.
- Website
- https://dataecho.ai/
- Repository
- https://github.com/mohocp/dataecho
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 419 ms |
| 22 hours ago | Handshake completed | 392 ms |
| 2 days ago | Handshake completed | 403 ms |
| 3 days ago | Handshake completed | 389 ms |
| 4 days ago | Handshake completed | 358 ms |
| 5 days ago | Handshake completed | 373 ms |
| 6 days ago | Handshake completed | 382 ms |
| 8 days ago | Handshake completed | 418 ms |
| 11 days ago | Handshake completed | 367 ms |
| 13 days ago | Handshake completed | 370 ms |
| 15 days ago | Handshake completed | 365 ms |
| 18 days ago | Handshake completed | 376 ms |
| 20 days ago | Handshake completed | 942 ms |
| 22 days ago | Handshake completed | 379 ms |
| 24 days ago | Handshake completed | 330 ms |
| 25 days ago | Handshake completed | 356 ms |
| 27 days ago | Handshake completed | 352 ms |
| 29 days ago | Handshake completed | 352 ms |
| 29 days ago | Handshake completed | 346 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 30.
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 ai.dataecho/mcp and makes no claim about it beyond what these checks measured.