> NOTICE — Pre-launch build. Every record here is a dated observation of a real MCP endpoint operated by a third party, rendered from the published archive. Coverage is partial — the figures cover the snapshots in the export this build was made from, not the whole chain and not the whole ecosystem. Claims and badges are not open.

# mcp.sematryx.com/sse

Last observed: 2026-08-30T08:25:04.457Z
Recorded as: TLS_FAIL (connection_reset)
Transport: sse
Observations held: 25
Published: yes

## Observations

| Observed | Snapshot | Recorded as | Detail | Latency ms | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| 2026-08-06T17:22:43.508Z | REL-SNAP-002 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-07T08:08:10.509Z | REL-SNAP-003 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-08T09:48:04.131Z | REL-SNAP-004 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-09T08:31:31.439Z | REL-SNAP-005 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-10T08:25:56.126Z | REL-SNAP-006 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-11T08:30:05.944Z | REL-SNAP-007 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-12T08:29:47.828Z | REL-SNAP-008 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-13T08:24:48.269Z | REL-SNAP-009 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-14T08:33:26.758Z | REL-SNAP-010 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-15T08:24:22.785Z | REL-SNAP-011 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-16T08:25:14.812Z | REL-SNAP-012 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-17T09:02:10.506Z | REL-SNAP-013 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-18T08:24:52.703Z | REL-SNAP-014 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-19T08:22:37.848Z | REL-SNAP-015 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-20T08:30:56.258Z | REL-SNAP-016 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-21T08:47:03.851Z | REL-SNAP-017 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-22T08:23:51.291Z | REL-SNAP-018 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-23T09:25:05.008Z | REL-SNAP-019 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-24T08:27:09.661Z | REL-SNAP-020 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-25T08:27:05.639Z | REL-SNAP-021 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-26T08:22:41.118Z | REL-SNAP-022 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-27T08:33:54.677Z | REL-SNAP-023 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-28T08:33:21.548Z | REL-SNAP-024 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-29T08:22:53.345Z | REL-SNAP-025 | TLS_FAIL | connection_reset | - | - | - |
| 2026-08-30T08:25:04.457Z | REL-SNAP-026 | TLS_FAIL | connection_reset | - | - | - |

## Identity

Record key: mcp.sematryx.com/sse (the normalised endpoint observed)
Registry names (not anchored — no inclusion proof reaches this field): 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)
Name reported by the server: not reported (self-reported, unverified, never used as identity)

Each observation carries a merkle leaf in the snapshot it belongs to. The chain
establishes that a root existed by a given time; it does not establish that any
measurement is true.