Remote Model Context Protocol server for DeFi vault data — 24 tools, no local setup required.
https://mcp.vaults.fyi/mcp
GET /health
An API key is required. Pass it via the Authorization: Bearer <key> header.
Method 1: Claude Connector (no local setup, requires Pro/Max/Enterprise)
vaults.fyi, URL: https://mcp.vaults.fyi/mcpMethod 2: Claude Desktop
Open Claude Desktop → Settings → Developer → Edit Config and add:
{
"mcpServers": {
"vaults": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.vaults.fyi/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}
Method 3: Claude Code
claude mcp add --transport http vaults https://mcp.vaults.fyi/mcp \ --header "Authorization: Bearer YOUR_API_KEY"
Add to your Codex MCP config:
{
"mcpServers": {
"vaults": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.vaults.fyi/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}
gemini mcp add vaults -- npx mcp-remote https://mcp.vaults.fyi/mcp \ --header "Authorization: Bearer YOUR_API_KEY"
Add to your MCP config (.cursor/mcp.json or equivalent):
{
"mcpServers": {
"vaults": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.vaults.fyi/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}
Any MCP client supporting Streamable HTTP transport can connect directly:
POST https://mcp.vaults.fyi/mcp Authorization: Bearer YOUR_API_KEY Content-Type: application/json Accept: application/json, text/event-stream
VaultsfyiActionProvider_vaults — Browse and filter vaults by network, asset, APY, TVLVaultsfyiActionProvider_detailed_vault — Get detailed vault infoVaultsfyiActionProvider_positions — View your vault positionsVaultsfyiActionProvider_user_idle_assets — Check wallet balancesVaultsfyiActionProvider_transaction_context — Get deposit/redeem stepsVaultsfyiActionProvider_execute_step — Execute vault actionsVaultsfyiActionProvider_benchmark_apy — Compare against benchmark yieldsTry asking: “Show me the best vaults on Base by APY”
Contact vaults.fyi support on Telegram or email [email protected].