zooq.dev/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-021 | OK | — | 297 | 44 | 26cfb503fad48585… | |
| REL-SNAP-022 | OK | — | 329 | 44 | b6c8588b8a1a06de… | |
| REL-SNAP-023 | OK | — | 284 | 44 | b6c8588b8a1a06de… | |
| REL-SNAP-024 | OK | — | 252 | 45 | 51b8570bb22858ee… | |
| REL-SNAP-025 | OK | — | 317 | 45 | 51b8570bb22858ee… | |
| REL-SNAP-026 | OK | — | 281 | 45 | 51b8570bb22858ee… |
Tool schema changed 2 times 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
zooq.dev/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.baldiga/zooq 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
- zooq 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.