mcp.sematryx.com/sse
Last observed:— recorded as TLS_FAIL (connection_reset)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-003 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-004 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-005 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-006 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-007 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-008 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-009 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-010 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-011 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-012 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-013 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-014 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-015 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-016 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-017 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-018 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-019 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-020 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-021 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-022 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-023 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-024 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-025 | TLS_FAIL | connection_reset | — | — | — | |
| REL-SNAP-026 | TLS_FAIL | connection_reset | — | — | — |
Identity
- Record key
mcp.sematryx.com/sse— the normalised endpoint observed. See the methodology for the rule.- Transport
- sse
- Registry names (not anchored)
- com.sematryx/optimizer 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
- Not reported. 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.