VaultVision Hyperliquid Vault Research
REMOTE · VAULTVISION.TECH
Read-only Hyperliquid vault search, risk, drawdown, rankings, TVL, alerts, and comparisons.
Available components
Last scanned (17 hours ago)
Scores higher than 93% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://vaultvision.tech/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vaultvision.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| vaultvision.tech. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vaultvision.tech/mcp | Unreachable | ||
| http (plaintext) | http://vaultvision.tech/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_vaults Compare Hyperliquid vaults ~45
Compare two to five current vault records side by side using the same timestamped fields. It does not choose a winner or allocate capital.
| Name | Type | Req | Description |
|---|---|---|---|
| vaults | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
explain_vault_risk Explain vault risk ~47
Explain one vault's current VaultVision risk score, component values, drawdown evidence, and data caveats without converting the model into investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| vault | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fetch Fetch VaultVision record ~38
Fetch one VaultVision search result by its vault: or page: identifier and return current structured evidence with a canonical URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_hlp_metrics Get HLP metrics ~45
Return the current VaultVision record for Hyperliquidity Provider (HLP), including timestamped TVL, performance, drawdown, risk, and deposit context when available.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_recent_alerts Get recent vault alerts ~57
Return recent rule-based VaultVision vault signals such as risk, entry, TVL, flow, or APR changes. Signals are monitoring context, not execution instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since_ts | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_vault Get one Hyperliquid vault ~53
Get the latest available VaultVision record for one vault ID, canonical slug, URL, or exact vault name, including risk, drawdown, entry, TVL, and deposit context.
| Name | Type | Req | Description |
|---|---|---|---|
| vault | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
rank_vaults Rank Hyperliquid vaults ~52
Return the current evidence-gated VaultVision ranking snapshot. Ranking is a first-party model and must not be presented as guaranteed future performance.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| ranking_type | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search Search VaultVision ~49
Search current Hyperliquid vault records and canonical VaultVision research pages. Use this standard discovery tool before fetch when the requested entity is ambiguous.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_vaults Search Hyperliquid vaults ~117
Filter and sort current Hyperliquid vaults by name, TVL, modeled risk, drawdown, entry quality, and observed deposit status. Returns evidence, not a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts_deposits | boolean | – | – |
| entry_label | string | – | – |
| limit | integer | – | – |
| max_drawdown_pct | number | – | – |
| max_risk_score | number | – | – |
| min_tvl_usd | number | – | – |
| query | string | – | – |
| sort_by | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the VaultVision Hyperliquid Vault Research MCP server?
VaultVision Hyperliquid Vault Research is a hosted endpoint at https://vaultvision.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vaultvision.tech
claude mcp add --transport http 0xkayser-vaultvision 'https://vaultvision.tech/mcp'
What is the VaultVision Hyperliquid Vault Research MCP server?
VaultVision Hyperliquid Vault Research is an MCP server listed in the public MCP registry as io.github.0xkayser/vaultvision. Read-only Hyperliquid vault search, risk, drawdown, rankings, TVL, alerts, and comparisons. This page covers its hosted endpoint (https://vaultvision.tech/mcp).
Is the VaultVision Hyperliquid Vault Research MCP server safe to use?
VaultVision Hyperliquid Vault Research scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VaultVision Hyperliquid Vault Research MCP server expose?
VaultVision Hyperliquid Vault Research exposes 9 tools: search, fetch, search_vaults, get_vault, rank_vaults, and 4 more. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.
Does the VaultVision Hyperliquid Vault Research MCP server require authentication?
Its publisher declares no required credentials for VaultVision Hyperliquid Vault Research. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the VaultVision Hyperliquid Vault Research MCP server still maintained?
VaultVision Hyperliquid Vault Research is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.