di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-012 | OK | — | 71 | 1 | c432dc9dad195160… | |
| REL-SNAP-013 | OK | — | 79 | 1 | c432dc9dad195160… | |
| REL-SNAP-014 | OK | — | 68 | 1 | c432dc9dad195160… | |
| REL-SNAP-015 | OK | — | 115 | 1 | c432dc9dad195160… | |
| REL-SNAP-016 | OK | — | 254 | 1 | c432dc9dad195160… |
Identity
- Record key
di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.scenicstay/lodging-decision-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
- di-001-a-lodging-decision 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.