rides.rs/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 1115 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-003 | OK | — | 1172 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-004 | OK | — | 1118 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-005 | OK | — | 1274 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-006 | OK | — | 1150 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-007 | OK | — | 1149 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-008 | OK | — | 1147 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-009 | OK | — | 1146 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-010 | OK | — | 1210 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-011 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-012 | OK | — | 1591 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-013 | OK | — | 1491 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-014 | OK | — | 1264 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-015 | OK | — | 194 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-016 | OK | — | 170 | 6 | 8f5cf82b70cb9041… | |
| REL-SNAP-017 | OK | — | 152 | — | — | |
| REL-SNAP-018 | OK | — | 181 | — | — | |
| REL-SNAP-019 | OK | — | 179 | — | — | |
| REL-SNAP-020 | OK | — | 229 | — | — | |
| REL-SNAP-021 | OK | — | 180 | — | — | |
| REL-SNAP-022 | OK | — | 179 | — | — | |
| REL-SNAP-023 | OK | — | 188 | — | — | |
| REL-SNAP-024 | OK | — | 244 | — | — | |
| REL-SNAP-025 | OK | — | 142 | — | — | |
| REL-SNAP-026 | OK | — | 243 | — | — |
Identity
- Record key
rides.rs/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- rs.rides/airport-transfers 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
- rides-rs 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.