base-tx-explain.fly.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-016 | OK | — | 274 | 1 | b9c1d41fbc1d612d… | |
| REL-SNAP-017 | OK | — | 316 | 2 | e705dba785c6a238… | |
| REL-SNAP-018 | OK | — | 412 | 2 | e705dba785c6a238… | |
| REL-SNAP-019 | OK | — | 362 | 2 | e705dba785c6a238… |
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
base-tx-explain.fly.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.0200project/base-tx-explain 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
- base-tx-explain 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.