agentread-json-api.army20160422.chatgpt.site/agent/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-054 | OK | — | 109 | 3 | 315b4057c3d34cc8… | |
| REL-SNAP-055 | OK | — | 131 | 3 | 315b4057c3d34cc8… | |
| REL-SNAP-056 | OK | — | 107 | 3 | 315b4057c3d34cc8… | |
| REL-SNAP-057 | OK | — | 94 | 3 | 315b4057c3d34cc8… | |
| REL-SNAP-058 | OK | — | 102 | 3 | 315b4057c3d34cc8… | |
| REL-SNAP-059 | OK | — | 82 | 3 | 315b4057c3d34cc8… |
Identity
- Record key
agentread-json-api.army20160422.chatgpt.site/agent/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- site.chatgpt.army20160422.agentread-json-api/agentread 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
- agentread 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.