handoff.notdown-app.workers.dev/mcp/%7Bkey%7D
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-022 | OK | — | 44 | 4 | b0fc91757d4b3c0a… | |
| REL-SNAP-023 | OK | — | 44 | 4 | b0fc91757d4b3c0a… | |
| REL-SNAP-024 | OK | — | 51 | 4 | 1419e6d7e68d754b… | |
| REL-SNAP-025 | OK | — | 55 | 4 | 1419e6d7e68d754b… | |
| REL-SNAP-026 | OK | — | 53 | 4 | 1419e6d7e68d754b… |
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
handoff.notdown-app.workers.dev/mcp/%7Bkey%7D— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- dev.workers.notdown-app.handoff/publish 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
- Handoff 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.