dadosb3.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 387 | 11 | e1856de1582db9b9… | |
| REL-SNAP-009 | OK | — | 412 | 14 | 072406da0aafdc96… | |
| REL-SNAP-010 | OK | — | 443 | 14 | 072406da0aafdc96… | |
| REL-SNAP-011 | OK | — | 540 | 14 | 072406da0aafdc96… | |
| REL-SNAP-012 | OK | — | 477 | 14 | 072406da0aafdc96… | |
| REL-SNAP-013 | OK | — | 410 | 14 | 072406da0aafdc96… | |
| REL-SNAP-014 | OK | — | 551 | 14 | 072406da0aafdc96… | |
| REL-SNAP-015 | OK | — | 380 | 14 | 072406da0aafdc96… | |
| REL-SNAP-016 | OK | — | 500 | 14 | 072406da0aafdc96… | |
| REL-SNAP-017 | OK | — | 534 | 14 | 072406da0aafdc96… | |
| REL-SNAP-018 | OK | — | 366 | 14 | 072406da0aafdc96… | |
| REL-SNAP-019 | OK | — | 551 | 14 | 072406da0aafdc96… | |
| REL-SNAP-020 | OK | — | 356 | 14 | 072406da0aafdc96… | |
| REL-SNAP-021 | OK | — | 396 | 14 | 072406da0aafdc96… | |
| REL-SNAP-022 | OK | — | 399 | 14 | 072406da0aafdc96… | |
| REL-SNAP-023 | OK | — | 369 | 15 | abd620b179c584b6… | |
| REL-SNAP-024 | OK | — | 666 | 15 | abd620b179c584b6… | |
| REL-SNAP-025 | OK | — | 434 | 15 | abd620b179c584b6… | |
| REL-SNAP-026 | OK | — | 377 | 15 | abd620b179c584b6… |
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
dadosb3.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.Val7h/dados-b3 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
- dados-b3 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.