api.0200project.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-020 | OK | — | 366 | 2 | e705dba785c6a238… | |
| REL-SNAP-021 | OK | — | 265 | 2 | e705dba785c6a238… | |
| REL-SNAP-022 | OK | — | 415 | 2 | e705dba785c6a238… | |
| REL-SNAP-023 | OK | — | 345 | 2 | e705dba785c6a238… | |
| REL-SNAP-024 | OK | — | 295 | 2 | e705dba785c6a238… | |
| REL-SNAP-025 | OK | — | 218 | 2 | e705dba785c6a238… | |
| REL-SNAP-026 | OK | — | 298 | 2 | e705dba785c6a238… |
Identity
- Record key
api.0200project.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.0200project/base-tx-explain, io.github.0200project/base-transaction-decoder 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. — more than one registry name refers to this single endpoint. We record both rather than choosing between them; the observation covers the endpoint and cannot be attributed to one of them.
- Name reported by the server
- base-transaction-decoder 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.