api.mcp.ai/p_cakto
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-021 | OK | — | 269 | 16 | 6ce62fb7894d80cc… | |
| REL-SNAP-022 | OK | — | 264 | 16 | 6ce62fb7894d80cc… | |
| REL-SNAP-023 | OK | — | 278 | 16 | 6ce62fb7894d80cc… | |
| REL-SNAP-024 | OK | — | 281 | 16 | 6ce62fb7894d80cc… | |
| REL-SNAP-025 | OK | — | 858 | 27 | 5adb203556065fef… | |
| REL-SNAP-026 | OK | — | 238 | 27 | 5adb203556065fef… |
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
api.mcp.ai/p_cakto— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.mcp-dir/cakto-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
- mcp-ai 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.