VaultVision Hyperliquid Vault Research
REMOTE · VAULTVISION.TECH · SCANNED SEP 20
Read-only Hyperliquid vault search, risk, drawdown, rankings, TVL, alerts, and comparisons.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 614 tokens (~68/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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'
{
"mcpServers": {
"0xkayser-vaultvision": {
"url": "https://vaultvision.tech/mcp"
}
}
} {
"servers": {
"0xkayser-vaultvision": {
"type": "http",
"url": "https://vaultvision.tech/mcp"
}
}
} [mcp_servers.0xkayser-vaultvision] url = "https://vaultvision.tech/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"0xkayser-vaultvision": {
"type": "remote",
"url": "https://vaultvision.tech/mcp",
"enabled": true
}
}
} openclaw mcp add 0xkayser-vaultvision --url 'https://vaultvision.tech/mcp' --transport streamable-http
mcp_servers:
0xkayser-vaultvision:
url: "https://vaultvision.tech/mcp" {
"McpServers": {
"0xkayser-vaultvision": {
"Transport": "http",
"Url": "https://vaultvision.tech/mcp"
}
}
} assistant mcp add 0xkayser-vaultvision -t streamable-http -u 'https://vaultvision.tech/mcp'
{
"mcpServers": {
"0xkayser-vaultvision": {
"type": "http",
"url": "https://vaultvision.tech/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://vaultvision.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vaultvision.tech | CN=YR2,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | RSA 2048 | SHA256-RSA | 6b69fc4ff24cc7891f704b597036cda0699 |
| SANs: vaultvision.tech | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
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 | Verified | 200 | |
| http (plaintext) | http://vaultvision.tech/mcp | HTTPS enforced | 301 | https://vaultvision.tech/mcp |
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.
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 83 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?
No. We connected to VaultVision Hyperliquid Vault Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VaultVision Hyperliquid Vault Research MCP server still maintained?
VaultVision Hyperliquid Vault Research is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.