opuslumiere.com/wp-json/opus-booking/v1/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-011 | OK | — | 935 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-012 | OK | — | 963 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-013 | OK | — | 644 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-014 | OK | — | 627 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-015 | OK | — | 325 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-016 | OK | — | 305 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-017 | OK | — | 331 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-018 | OK | — | 331 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-019 | OK | — | 368 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-020 | OK | — | 318 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-021 | OK | — | 326 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-022 | OK | — | 326 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-023 | OK | — | 357 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-024 | OK | — | 342 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-025 | OK | — | 345 | 4 | 5b1f1bf7bf56f470… | |
| REL-SNAP-026 | OK | — | 332 | 4 | 5b1f1bf7bf56f470… |
Identity
- Record key
opuslumiere.com/wp-json/opus-booking/v1/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.opuslumiere/booking 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
- Opus Lumière Booking 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.