sub1.find-me.casa
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 1824 | — | — | |
| REL-SNAP-003 | OK | — | 1896 | — | — | |
| REL-SNAP-004 | PROTOCOL_ERROR | mcp_error_32603 | — | — | — | |
| REL-SNAP-005 | OK | — | 890 | — | — | |
| REL-SNAP-006 | OK | — | 680 | — | — | |
| REL-SNAP-007 | OK | — | 1417 | — | — | |
| REL-SNAP-008 | OK | — | 1815 | — | — | |
| REL-SNAP-009 | OK | — | 1811 | — | — | |
| REL-SNAP-010 | OK | — | 944 | — | — | |
| REL-SNAP-011 | OK | — | 899 | — | — | |
| REL-SNAP-012 | OK | — | 881 | — | — | |
| REL-SNAP-013 | OK | — | 1423 | — | — | |
| REL-SNAP-014 | OK | — | 1642 | — | — | |
| REL-SNAP-015 | OK | — | 1561 | — | — | |
| REL-SNAP-016 | OK | — | 547 | — | — | |
| REL-SNAP-017 | OK | — | 1528 | — | — | |
| REL-SNAP-018 | OK | — | 1701 | — | — | |
| REL-SNAP-019 | OK | — | 380 | — | — | |
| REL-SNAP-020 | OK | — | 1541 | — | — | |
| REL-SNAP-021 | OK | — | 1532 | — | — | |
| REL-SNAP-022 | OK | — | 1547 | — | — | |
| REL-SNAP-023 | OK | — | 395 | — | — | |
| REL-SNAP-024 | OK | — | 468 | — | — | |
| REL-SNAP-025 | OK | — | 1519 | — | — | |
| REL-SNAP-026 | OK | — | 406 | — | — |
Identity
- Record key
sub1.find-me.casa— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- casa.find-me.sub1/send-email-mcp 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
- Resend Email 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.