api.delx.ai/v1/mcp/protocol
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-010 | OK | — | 966 | — | — | |
| REL-SNAP-011 | OK | — | 434 | — | — | |
| REL-SNAP-012 | OK | — | 931 | — | — | |
| REL-SNAP-013 | OK | — | 888 | — | — | |
| REL-SNAP-014 | OK | — | 904 | — | — | |
| REL-SNAP-015 | OK | — | 129 | — | — | |
| REL-SNAP-016 | OK | — | 119 | — | — |
Identity
- Record key
api.delx.ai/v1/mcp/protocol— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.davidmosiah/delx-protocol What the registry said when we swept it, as observed by us — not evidence that the registry was correct, that the name belongs to whoever registered it, or that it still resolves. Not covered by the chain: no inclusion proof reaches this field.
- Name reported by the server
- Delx Agent Operations Protocol Self-reported and unverified — never used as identity.
Verifying this record
Each observation above carries a merkle leaf in the published snapshot it belongs to. Verify the chain explains how to walk a leaf to a published root without taking our word for any of it.