api-production-9502.up.railway.app/mcp
Last observed:— recorded as HTTP_4XX (http_404)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-006 | OK | — | 478 | 32 | 18a13b441f683926… | |
| REL-SNAP-007 | OK | — | 454 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-008 | OK | — | 492 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-009 | OK | — | 458 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-010 | OK | — | 582 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-011 | OK | — | 462 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-012 | OK | — | 699 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-013 | OK | — | 510 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-014 | OK | — | 452 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-015 | OK | — | 360 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-016 | OK | — | 577 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-017 | OK | — | 351 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-018 | OK | — | 356 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-019 | OK | — | 370 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-020 | OK | — | 470 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-021 | OK | — | 529 | 32 | 564a33e73d2c4f80… | |
| REL-SNAP-022 | HTTP_4XX | http_404 | — | — | — | |
| REL-SNAP-023 | HTTP_4XX | http_404 | — | — | — | |
| REL-SNAP-024 | HTTP_4XX | http_404 | — | — | — | |
| REL-SNAP-025 | HTTP_4XX | http_404 | — | — | — | |
| REL-SNAP-026 | HTTP_4XX | http_404 | — | — | — |
Tool schema changed 1 time across this history — the fingerprint differs between consecutive observations. A change can occur while the tool count stays identical, which is why the fingerprint is recorded alongside the count.
Identity
- Record key
api-production-9502.up.railway.app/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.juodoc/ap-control 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
- Not reported. 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.