vaults.fyi MCP v2

Remote Streamable HTTP MCP server for vaults.fyi V2 data and unsigned transaction construction.

38 native v2 toolsNo server private keys

MCP endpoint: https://mcp.vaults.fyi/mcp

Health check: GET /health

Initialize with Authorization: Bearer <VAULTS_API_KEY>. The API key is forwarded only to vaults.fyi API calls and is never placed in signing URLs.

Quick setup

Run the one-line installer to configure the vaults.fyi MCP server in your AI client:

npx @vaultsfyi/scripts init-mcp

The script detects your client (Claude Desktop, Claude Code, Cursor, etc.), prompts for your API key, and writes the config automatically.

Prefer to set things up by hand? See the manual setup guide →

Representative tools

networks

List supported networks.

vaults_search

Search/filter detailed V2 vaults.

positions

Read user vault positions.

build_vault_tx

Build unsigned vault transaction steps.

transfer_erc20

Build unsigned ERC20 transfer calldata.

submit_tx_hash

Record a signed transaction hash.

Signing model

vaults.fyi MCP v2 never asks for, stores, or uses a wallet private key. Transaction tools return unsigned transaction steps plus a short-lived browser signingUrl.

  1. If OWS or another signing MCP is configured, pass the returned unsignedTx to that tool.
  2. If no signing MCP is available, open the returned signingUrl and sign in your browser wallet.
  3. After broadcast, call submit_tx_hash, then get_transaction_status.
Verify the URL is under https://mcp.vaults.fyi, the wallet and network match the transaction, and the destination/value/calldata are expected. Never paste a seed phrase or private key into vaults.fyi MCP.
Powered by vaults.fyi