mcp.bancadia.com
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 551 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-009 | OK | — | 768 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-010 | OK | — | 521 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-011 | OK | — | 517 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-012 | OK | — | 616 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-013 | OK | — | 526 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-014 | OK | — | 538 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-015 | OK | — | 346 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-016 | OK | — | 457 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-017 | OK | — | 505 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-018 | OK | — | 385 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-019 | OK | — | 469 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-020 | OK | — | 642 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-021 | OK | — | 522 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-022 | OK | — | 453 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-023 | OK | — | 372 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-024 | OK | — | 466 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-025 | OK | — | 470 | 2 | 959b18ae78315e9d… | |
| REL-SNAP-026 | OK | — | 476 | 2 | 959b18ae78315e9d… |
Identity
- Record key
mcp.bancadia.com— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.macphe22/bancadia-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
- Bancadia MCP 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.