apisecurityscan.net/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-003 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-004 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-005 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-006 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-007 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-008 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-009 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-010 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-011 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-012 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-013 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-014 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-015 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-016 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-017 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-018 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-019 | TLS_FAIL | fetch_failed | — | — | — | |
| REL-SNAP-020 | OK | — | 179 | 6 | cb00818f27f840f8… | |
| REL-SNAP-021 | OK | — | 248 | 6 | cb00818f27f840f8… | |
| REL-SNAP-022 | OK | — | 103 | 6 | cb00818f27f840f8… | |
| REL-SNAP-023 | OK | — | 341 | 6 | cb00818f27f840f8… | |
| REL-SNAP-024 | OK | — | 75 | 6 | cb00818f27f840f8… | |
| REL-SNAP-025 | OK | — | 120 | 6 | cb00818f27f840f8… | |
| REL-SNAP-026 | OK | — | 26 | 8 | 6acebdfc31366f2e… |
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
apisecurityscan.net/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- net.apisecurityscan/securityscan 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
- SecurityScan 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.