getyo.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-005 | OK | — | 605 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-006 | OK | — | 611 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-007 | OK | — | 574 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-008 | OK | — | 788 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-009 | OK | — | 684 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-010 | OK | — | 598 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-011 | OK | — | 586 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-012 | OK | — | 660 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-013 | OK | — | 884 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-014 | OK | — | 654 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-015 | OK | — | 419 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-016 | OK | — | 539 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-017 | OK | — | 288 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-018 | OK | — | 475 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-019 | OK | — | 427 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-020 | OK | — | 437 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-021 | OK | — | 343 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-022 | OK | — | 465 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-023 | OK | — | 392 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-024 | OK | — | 290 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-025 | OK | — | 314 | 5 | 1cab7922ded13adf… | |
| REL-SNAP-026 | OK | — | 580 | 5 | 1cab7922ded13adf… |
Identity
- Record key
getyo.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.alfongj-com/yo 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
- yo 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.