Home / MCP registry index / io.philidor/defi-vaults

Philidor DeFi Vault Risk Analytics

io.philidor/defi-vaults in the official MCP registry. Endpoint https://mcp.philidor.io/api/mcp. Source: github.com/Philidor-Labs/philidor-mcp.

The registry describes it as: Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http defi-vaults https://mcp.philidor.io/api/mcp

{
  "mcpServers": {
    "defi-vaults": {
      "url": "https://mcp.philidor.io/api/mcp"
    }
  }
}

code --add-mcp '{"name":"defi-vaults","type":"http","url":"https://mcp.philidor.io/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_vaults get_vault get_vault_risk_breakdown list_markets get_market get_market_events check_loop_venue list_ondo_assets get_ondo_asset get_ondo_asset_stream get_ondo_asset_data get_native_asset_assessment get_native_asset_financials compare_vaults find_safest_vaults get_protocol_info get_curator_info get_market_overview explain_risk_score list_vaults_with_incidents check_policy list_baskets list_rwa get_oracles

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): d518b75a0ffb7606. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-philidor-defi-vaults/badge.svg)](https://lazaretto.dev/mcp-registry/io-philidor-defi-vaults)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers · Analytics and SEO MCP servers