# VaultVision Hyperliquid Vault Research (remote · vaultvision.tech)

Read-only Hyperliquid vault search, risk, drawdown, rankings, TVL, alerts, and comparisons.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `vaultvision.tech`: 83/100 (this document), [markdown](https://verifymcp.io/servers/0xkayser-vaultvision/vaultvision.md), [page](https://verifymcp.io/servers/0xkayser-vaultvision/vaultvision)

## Channel facts

- Endpoint: `https://vaultvision.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 614 tokens (~68/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http 0xkayser-vaultvision 'https://vaultvision.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "0xkayser-vaultvision": {
      "url": "https://vaultvision.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "0xkayser-vaultvision": {
      "type": "http",
      "url": "https://vaultvision.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.0xkayser-vaultvision]
url = "https://vaultvision.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "0xkayser-vaultvision": {
      "type": "remote",
      "url": "https://vaultvision.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 0xkayser-vaultvision --url 'https://vaultvision.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  0xkayser-vaultvision:
    url: "https://vaultvision.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "0xkayser-vaultvision": {
      "Transport": "http",
      "Url": "https://vaultvision.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 0xkayser-vaultvision -t streamable-http -u 'https://vaultvision.tech/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 83, +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.

### 2026-09-16 (score 82, +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.

### 2026-09-14 (score 81, +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.

### 2026-09-12 (score 80, +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.

### 2026-09-10 (score 79, +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.

### 2026-09-08 (score 78, +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.

### 2026-09-06 (score 77, +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.

### 2026-09-04 (score 76, +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.

## MCP tools (9)

### `search` (~49 tokens)

Search VaultVision

Search current Hyperliquid vault records and canonical VaultVision research pages. Use this standard discovery tool before fetch when the requested entity is ambiguous.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `fetch` (~38 tokens)

Fetch VaultVision record

Fetch one VaultVision search result by its vault: or page: identifier and return current structured evidence with a canonical URL.

Input parameters:

- `id` (string, required)

### `search_vaults` (~117 tokens)

Search Hyperliquid vaults

Filter and sort current Hyperliquid vaults by name, TVL, modeled risk, drawdown, entry quality, and observed deposit status. Returns evidence, not a recommendation.

Input parameters:

- `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)

### `get_vault` (~53 tokens)

Get one Hyperliquid vault

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.

Input parameters:

- `vault` (string, required)

### `rank_vaults` (~52 tokens)

Rank Hyperliquid vaults

Return the current evidence-gated VaultVision ranking snapshot. Ranking is a first-party model and must not be presented as guaranteed future performance.

Input parameters:

- `limit` (integer)
- `ranking_type` (string)

### `compare_vaults` (~45 tokens)

Compare Hyperliquid vaults

Compare two to five current vault records side by side using the same timestamped fields. It does not choose a winner or allocate capital.

Input parameters:

- `vaults` (array, required)

### `explain_vault_risk` (~47 tokens)

Explain vault risk

Explain one vault's current VaultVision risk score, component values, drawdown evidence, and data caveats without converting the model into investment advice.

Input parameters:

- `vault` (string, required)

### `get_hlp_metrics` (~45 tokens)

Get HLP metrics

Return the current VaultVision record for Hyperliquidity Provider (HLP), including timestamped TVL, performance, drawdown, risk, and deposit context when available.

### `get_recent_alerts` (~57 tokens)

Get recent vault alerts

Return recent rule-based VaultVision vault signals such as risk, entry, TVL, flow, or APR changes. Signals are monitoring context, not execution instructions.

Input parameters:

- `limit` (integer)
- `since_ts` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/0xkayser-vaultvision/vaultvision#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 82
- 2026-09-15: 81
- 2026-09-14: 81
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 75
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 73
- 2026-08-28: 73
- 2026-08-27: 72

## Common questions

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

## Links

- Remote endpoint: https://vaultvision.tech/mcp
- Repository: https://github.com/0xkayser/vaultvision-mcp
- Website: https://vaultvision.tech/developers#agents
- Changelog RSS feed: https://verifymcp.io/servers/0xkayser-vaultvision/vaultvision.xml
- Changelog JSON feed: https://verifymcp.io/servers/0xkayser-vaultvision/vaultvision.json
- HTML version of this page: https://verifymcp.io/servers/0xkayser-vaultvision/vaultvision