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

# vaultvision.tech/mcp

Last observed: 2026-08-30T09:18:13.268Z
Recorded as: OK
Transport: streamable-http
Observations held: 3
Published: yes

## Observations

| Observed | Snapshot | Recorded as | Detail | Latency ms | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| 2026-08-28T09:26:15.253Z | REL-SNAP-024 | OK | - | 393 | 9 | 54a3d6adb2aebe517d21cc9528a2068e1ff6f98c2bd6025ce9278d9b525c44b4 |
| 2026-08-29T09:15:54.476Z | REL-SNAP-025 | OK | - | 511 | 9 | 54a3d6adb2aebe517d21cc9528a2068e1ff6f98c2bd6025ce9278d9b525c44b4 |
| 2026-08-30T09:18:13.268Z | REL-SNAP-026 | OK | - | 346 | 9 | 54a3d6adb2aebe517d21cc9528a2068e1ff6f98c2bd6025ce9278d9b525c44b4 |

## Identity

Record key: vaultvision.tech/mcp (the normalised endpoint observed)
Registry names (not anchored — no inclusion proof reaches this field): io.github.0xkayser/vaultvision (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: vaultvision-hyperliquid-vaults (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.
