> 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.

# 3dtexel.com/wp-json/3dtexel-api/v1/mcp

Last observed: 2026-10-02T09:44:29.989Z
Recorded as: OK
Transport: streamable-http
Observations held: 3
Published: yes

## Observations

| Observed | Snapshot | Recorded as | Detail | Latency ms | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| 2026-09-30T10:14:53.573Z | REL-SNAP-057 | OK | - | 501 | 16 | 246b1f728bc8fab990f582a5ae015bab1aa05f57dfdd6953fe6c24c8ac850eea |
| 2026-10-01T09:48:56.086Z | REL-SNAP-058 | OK | - | 458 | 16 | 246b1f728bc8fab990f582a5ae015bab1aa05f57dfdd6953fe6c24c8ac850eea |
| 2026-10-02T09:44:29.989Z | REL-SNAP-059 | OK | - | 528 | 16 | 246b1f728bc8fab990f582a5ae015bab1aa05f57dfdd6953fe6c24c8ac850eea |

## Identity

Record key: 3dtexel.com/wp-json/3dtexel-api/v1/mcp (the normalised endpoint observed)
Registry names (not anchored — no inclusion proof reaches this field): com.3dtexel/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)
Name reported by the server: 3dtexel (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.