twothumbs.co/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 540 | 3 | fb3b8e37501dbe91… | |
| REL-SNAP-010 | OK | — | 406 | 3 | babf1a28ad050aea… | |
| REL-SNAP-011 | OK | — | 356 | 3 | babf1a28ad050aea… | |
| REL-SNAP-012 | OK | — | 363 | 3 | babf1a28ad050aea… | |
| REL-SNAP-013 | OK | — | 322 | 3 | babf1a28ad050aea… | |
| REL-SNAP-014 | OK | — | 355 | 3 | babf1a28ad050aea… | |
| REL-SNAP-015 | OK | — | 332 | 3 | babf1a28ad050aea… | |
| REL-SNAP-016 | OK | — | 887 | 3 | babf1a28ad050aea… | |
| REL-SNAP-017 | OK | — | 371 | 3 | babf1a28ad050aea… | |
| REL-SNAP-018 | OK | — | 468 | 3 | babf1a28ad050aea… | |
| REL-SNAP-019 | OK | — | 383 | 3 | babf1a28ad050aea… | |
| REL-SNAP-020 | OK | — | 426 | 3 | babf1a28ad050aea… | |
| REL-SNAP-021 | OK | — | 366 | 3 | babf1a28ad050aea… | |
| REL-SNAP-022 | OK | — | 395 | 3 | babf1a28ad050aea… | |
| REL-SNAP-023 | OK | — | 365 | 3 | babf1a28ad050aea… | |
| REL-SNAP-024 | OK | — | 407 | 3 | babf1a28ad050aea… | |
| REL-SNAP-025 | OK | — | 389 | 3 | babf1a28ad050aea… | |
| REL-SNAP-026 | OK | — | 378 | 3 | babf1a28ad050aea… |
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
twothumbs.co/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.asselwan/twothumbs 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
- twothumbs 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.