mog-concierge.33guruge.workers.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-011 | OK | — | 33 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-012 | OK | — | 91 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-013 | OK | — | 37 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-014 | OK | — | 53 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-015 | OK | — | 44 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-016 | OK | — | 173 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-017 | OK | — | 59 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-018 | OK | — | 52 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-019 | OK | — | 53 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-020 | OK | — | 47 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-021 | OK | — | 49 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-022 | OK | — | 57 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-023 | OK | — | 44 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-024 | OK | — | 90 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-025 | OK | — | 48 | 3 | 0aa9e703b8d5b9e9… | |
| REL-SNAP-026 | OK | — | 44 | 3 | 0aa9e703b8d5b9e9… |
Identity
- Record key
mog-concierge.33guruge.workers.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- au.com.ministryofgems/gemmology 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
- ministry-of-gems-gemmology 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.