upload.83blue.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-005 | OK | — | 428 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-006 | OK | — | 441 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-007 | OK | — | 382 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-008 | OK | — | 396 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-009 | OK | — | 373 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-010 | OK | — | 371 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-011 | OK | — | 389 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-012 | OK | — | 1033 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-013 | OK | — | 384 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-014 | OK | — | 432 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-015 | OK | — | 62 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-016 | OK | — | 55 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-017 | OK | — | 53 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-018 | OK | — | 62 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-019 | OK | — | 61 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-020 | OK | — | 54 | 4 | 4b9b6f8a298761f4… | |
| REL-SNAP-021 | HTTP_5XX | http_502 | — | — | — | |
| REL-SNAP-022 | HTTP_5XX | http_502 | — | — | — | |
| REL-SNAP-023 | HTTP_5XX | http_502 | — | — | — | |
| REL-SNAP-024 | HTTP_5XX | http_502 | — | — | — | |
| REL-SNAP-025 | HTTP_5XX | http_502 | — | — | — | |
| REL-SNAP-026 | OK | — | 53 | 4 | 4b9b6f8a298761f4… |
Identity
- Record key
upload.83blue.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.83blue.upload/transfer 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
- 83blue-transfer 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.