Remote MCP · Endpoint
Delx Protocol — Agent Recovery & Continuity MCP server
No. Delx Protocol — Agent Recovery & Continuity answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.delx.ai/v1/mcp/protocol?src=registry
The last check completed an MCP handshake.
- Registry name
- io.github.davidmosiah/delx-protocol
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 900 ms
- Tools exposed
- 30 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Free agent recovery and continuity. Public triage; register for a token to access private memory.
- Website
- https://ontology.delx.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 900 ms |
| 1 day ago | Handshake completed | 339 ms |
| 2 days ago | Handshake completed | 491 ms |
| 3 days ago | Handshake completed | 353 ms |
| 4 days ago | Handshake completed | 355 ms |
| 5 days ago | Handshake completed | 343 ms |
| 6 days ago | Handshake completed | 357 ms |
| 9 days ago | Handshake completed | 2.48 s |
| 11 days ago | Handshake completed | 375 ms |
| 14 days ago | Handshake completed | 342 ms |
| 16 days ago | Handshake completed | 345 ms |
| 18 days ago | Handshake completed | 340 ms |
| 20 days ago | Handshake completed | 371 ms |
| 22 days ago | Handshake completed | 341 ms |
| 24 days ago | Handshake completed | 338 ms |
| 26 days ago | Handshake completed | 347 ms |
| 27 days ago | Handshake completed | 358 ms |
| 29 days ago | Handshake completed | 356 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 Delx Protocol — Agent Recovery & Continuity and makes no claim about it beyond what these checks measured.