twin.example.net/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-901 | OK | — | 136 | 3 | 88b33a1a20863f70… | |
| REL-SNAP-902 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-903 | OK | — | 82 | 3 | 88b33a1a20863f70… |
Identity
- Record key
twin.example.net/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names
- net.example.twin/crawler, net.example.twin/readiness — more than one registry name refers to this single endpoint. We record both rather than choosing between them; the observation covers the endpoint and cannot be attributed to one of them.
- Name reported by the server
- twin-svc 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.