api.chasa.io/mcp
Last observed:— recorded as PROTOCOL_ERROR (schema_validation_failed)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-012 | OK | — | 794 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-013 | OK | — | 769 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-014 | OK | — | 930 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-015 | OK | — | 201 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-016 | OK | — | 198 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-017 | OK | — | 238 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-018 | OK | — | 232 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-019 | OK | — | 205 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-020 | OK | — | 220 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-021 | OK | — | 220 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-022 | OK | — | 220 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-023 | OK | — | 212 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-024 | OK | — | 239 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-025 | OK | — | 207 | 4 | d530a2e0f80fad38… | |
| REL-SNAP-026 | PROTOCOL_ERROR | schema_validation_failed | — | — | — |
Identity
- Record key
api.chasa.io/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.docracy1/chasa 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
- Not reported. 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.