clearbounce.net/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-010 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-011 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-012 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-013 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-014 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-015 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-016 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-017 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-018 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-019 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-020 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-021 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-022 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-023 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-024 | AUTH_REQUIRED | http_401 | — | — | — | |
| REL-SNAP-025 | OK | — | 26 | 5 | 072ed6d0c5eee362… | |
| REL-SNAP-026 | OK | — | 26 | 5 | 072ed6d0c5eee362… |
Identity
- Record key
clearbounce.net/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- net.clearbounce/email-verification 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
- clearbounce 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.