api.cinderroute.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-038 | OK | — | 652 | 8 | 99a11273716648df… | |
| REL-SNAP-039 | OK | — | 687 | 8 | 99a11273716648df… | |
| REL-SNAP-040 | OK | — | 681 | 8 | 99a11273716648df… | |
| REL-SNAP-041 | OK | — | 719 | 8 | 99a11273716648df… | |
| REL-SNAP-042 | OK | — | 659 | 8 | 99a11273716648df… | |
| REL-SNAP-043 | OK | — | 661 | 8 | 99a11273716648df… | |
| REL-SNAP-044 | OK | — | 704 | 8 | 99a11273716648df… | |
| REL-SNAP-045 | OK | — | 657 | 8 | 99a11273716648df… | |
| REL-SNAP-046 | OK | — | 649 | 8 | 99a11273716648df… | |
| REL-SNAP-047 | OK | — | 701 | 8 | 99a11273716648df… | |
| REL-SNAP-048 | OK | — | 744 | 8 | 99a11273716648df… | |
| REL-SNAP-049 | OK | — | 642 | 8 | 99a11273716648df… | |
| REL-SNAP-050 | OK | — | 691 | 8 | 99a11273716648df… | |
| REL-SNAP-051 | OK | — | 660 | 8 | 99a11273716648df… | |
| REL-SNAP-052 | OK | — | 436 | 8 | 99a11273716648df… | |
| REL-SNAP-053 | OK | — | 440 | 8 | 99a11273716648df… | |
| REL-SNAP-054 | OK | — | 437 | 8 | 99a11273716648df… | |
| REL-SNAP-055 | OK | — | 446 | 8 | 99a11273716648df… | |
| REL-SNAP-056 | OK | — | 439 | 8 | 99a11273716648df… | |
| REL-SNAP-057 | OK | — | 448 | 8 | 99a11273716648df… | |
| REL-SNAP-058 | OK | — | 444 | 8 | 99a11273716648df… | |
| REL-SNAP-059 | OK | — | 435 | 8 | 99a11273716648df… |
Identity
- Record key
api.cinderroute.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- dev.cinderroute/agentic-ci-operations 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
- cinderroute-ci-agent 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.