agentxray.ai/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-029 | OK | — | 85 | — | — | |
| REL-SNAP-030 | OK | — | 265 | — | — | |
| REL-SNAP-031 | OK | — | 82 | — | — | |
| REL-SNAP-032 | OK | — | 84 | — | — | |
| REL-SNAP-033 | OK | — | 108 | — | — | |
| REL-SNAP-034 | OK | — | 86 | — | — | |
| REL-SNAP-035 | OK | — | 125 | — | — | |
| REL-SNAP-036 | OK | — | 102 | — | — | |
| REL-SNAP-037 | OK | — | 284 | — | — | |
| REL-SNAP-038 | OK | — | 159 | — | — | |
| REL-SNAP-039 | OK | — | 588 | — | — | |
| REL-SNAP-040 | OK | — | 103 | — | — | |
| REL-SNAP-041 | OK | — | 125 | — | — | |
| REL-SNAP-042 | OK | — | 112 | — | — | |
| REL-SNAP-043 | OK | — | 286 | — | — | |
| REL-SNAP-044 | OK | — | 396 | — | — | |
| REL-SNAP-045 | OK | — | 121 | — | — | |
| REL-SNAP-046 | OK | — | 123 | — | — | |
| REL-SNAP-047 | OK | — | 146 | — | — | |
| REL-SNAP-048 | OK | — | 117 | — | — | |
| REL-SNAP-049 | OK | — | 126 | — | — | |
| REL-SNAP-050 | OK | — | 158 | — | — | |
| REL-SNAP-051 | OK | — | 159 | — | — | |
| REL-SNAP-052 | OK | — | 85 | — | — | |
| REL-SNAP-053 | OK | — | 70 | — | — | |
| REL-SNAP-054 | OK | — | 75 | — | — | |
| REL-SNAP-055 | OK | — | 99 | — | — | |
| REL-SNAP-056 | OK | — | 88 | — | — | |
| REL-SNAP-057 | OK | — | 128 | — | — | |
| REL-SNAP-058 | OK | — | 109 | — | — | |
| REL-SNAP-059 | OK | — | 99 | — | — |
Identity
- Record key
agentxray.ai/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- ai.agentxray/mcp 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
- agentxray 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.