`vaultvision.tech/mcp`

Last observed:2026-08-30T09:18:13.268Z— recorded as OK

Observations

Every observation recorded for this endpoint, oldest first. Each row is a separate look, not a summary.
Observed	Snapshot	Recorded as	Detail	Latency (ms)	Tools	Tool schema fingerprint
2026-08-28T09:26:15.253Z	REL-SNAP-024	OK	—	393	9	`54a3d6adb2aebe51…`
2026-08-29T09:15:54.476Z	REL-SNAP-025	OK	—	511	9	`54a3d6adb2aebe51…`
2026-08-30T09:18:13.268Z	REL-SNAP-026	OK	—	346	9	`54a3d6adb2aebe51…`

Identity

Record key: vaultvision.tech/mcp — the normalised endpoint observed. See the methodology for the rule.
Transport: streamable-http
Registry names (not anchored): 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. Not covered by the chain: no inclusion proof reaches this field.
Name reported by the server: vaultvision-hyperliquid-vaults 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.

Plain-text version of this page