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

# api.diglabo.com/kanji/mcp-guest

Last observed: 2026-10-02T09:51:01.998Z
Recorded as: OK
Transport: streamable-http
Observations held: 2
Published: no — below the threshold of 3 observations

## Observations

| Observed | Snapshot | Recorded as | Detail | Latency ms | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| 2026-10-01T09:54:03.716Z | REL-SNAP-058 | OK | - | 78 | 4 | f59a79a41d1fca89cb1fc6ef2baec208ef98c3f2dc00148e0e04d52f0ec5240c |
| 2026-10-02T09:51:01.998Z | REL-SNAP-059 | OK | - | 87 | 4 | f7ab04bd86615a5205fe9bc7d49e2729593ba4ded437a9314fdbd8230200de21 |

## Identity

Record key: api.diglabo.com/kanji/mcp-guest (the normalised endpoint observed)
Registry names (not anchored — no inclusion proof reaches this field): com.diglabo/kanji-prints (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: diglabo-kanji (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.