breach.seiche.info/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 757 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-003 | OK | — | 839 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-004 | OK | — | 834 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-005 | OK | — | 800 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-006 | OK | — | 1036 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-007 | OK | — | 855 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-008 | OK | — | 438 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-009 | OK | — | 756 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-010 | OK | — | 754 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-011 | OK | — | 791 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-012 | OK | — | 1042 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-013 | OK | — | 780 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-014 | OK | — | 828 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-015 | OK | — | 35 | 7 | 773f79f80b7b92ea… | |
| REL-SNAP-016 | OK | — | 56 | 7 | 773f79f80b7b92ea… |
Identity
- Record key
breach.seiche.info/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.beepboop2025/data-breach-detector 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
- data-breach-detector 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.