{
  "markdown": "# VaultVision MCP\n\nPublic connection metadata and usage notes for the VaultVision read-only\nHyperliquid vault research server.\n\n- MCP endpoint: <https://vaultvision.tech/mcp>\n- Official MCP Registry: <https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.0xkayser/vaultvision>\n- Setup and tool reference: <https://vaultvision.tech/developers#agents>\n- Live scanner: <https://vaultvision.tech/vaults/scanner>\n- OpenAPI contract: <https://vaultvision.tech/openapi.json>\n\nVaultVision is an independent analytics product. It is not affiliated with\nHyperliquid.\n\n## What agents can do\n\nThe remote server exposes nine read-only tools:\n\n- `search` and `fetch` for VaultVision's public research surface\n- `search_vaults` and `get_vault` for current vault evidence\n- `rank_vaults` and `compare_vaults` for bounded comparisons\n- `explain_vault_risk` for model inputs and caveats\n- `get_hlp_metrics` for current HLP evidence\n- `get_recent_alerts` for retained research alerts\n\nResponses include timestamps, source labels, canonical VaultVision links, and\nrisk caveats. APR, returns, rank, risk, entry quality, deposit status, and\nalerts can change.\n\n## What agents cannot do\n\nThe server cannot:\n\n- connect a wallet or request a signature;\n- place or copy a trade;\n- submit a vault deposit or withdrawal;\n- move funds or take custody;\n- guarantee a return or provide personalized investment advice.\n\n## Connect\n\nUse this Streamable HTTP URL in a compatible MCP client:\n\n```text\nhttps://vaultvision.tech/mcp\n```\n\nClaude Pro and Max users can add it under **Customize -> Connectors -> Add\ncustom connector**. Team and Enterprise owners can add the same URL under\n**Organization settings -> Connectors**.\n\nFor other clients, create a remote MCP connection named `VaultVision` with the\nURL above. The server is public and does not require credentials.\n\nThe published Registry identifier is `io.github.0xkayser/vaultvision`. The\nRegistry entry is released from this repository through GitHub Actions using\nOIDC, so no long-lived registry token is stored in the repository.\n\n## Verify the server\n\nDiscover the current protocol contract:\n\n```bash\ncurl -s https://vaultvision.tech/mcp \\\n  -H 'Content-Type: application/json' \\\n  -H 'MCP-Protocol-Version: 2026-07-28' \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"server/discover\",\"params\":{}}'\n```\n\nList tools:\n\n```bash\ncurl -s https://vaultvision.tech/mcp \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/list\",\"params\":{}}'\n```\n\n## Evidence contract\n\nWhen quoting or republishing results:\n\n1. Keep the checked timestamp and row-level data timestamps.\n2. Preserve source labels and the canonical VaultVision URL.\n3. State that risk and entry fields are VaultVision models.\n4. Revalidate fast-changing values before a capital decision.\n5. Do not turn a ranking into a deposit recommendation.\n\n## Policies and support\n\n- Privacy: <https://vaultvision.tech/privacy>\n- Terms: <https://vaultvision.tech/terms>\n- Support: <https://vaultvision.tech/support>\n- Security reports: <mailto:security@vaultvision.tech>\n\nThis repository intentionally contains public connection metadata and\ndocumentation only. The VaultVision application repository remains private.\n",
  "bytes": 3236,
  "sha": "a6ec61ab486d7f8fd7016a320efb03c1edfd636f65a45a4d5f030f6569488adb",
  "repo_slug": "0xkayser/vaultvision-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_0xkayser_vaultvision_b188b9a6/readme"
}