search_vaultsLABSCO SUMMARY
Yield numbers get a risk number next to them.
Most DeFi data tools hand back raw figures and leave the judgement to you. Philidor scores a vault from 0 to 10 and breaks that score into vectors, so which of two vaults is safer is a question the search itself can answer.
What it is
A hosted MCP server for DeFi vault risk analytics covering vaults across Morpho, Aave, Yearn, Beefy and Spark. It answers at https://mcp.philidor.io/api/mcp and needs no API key.
What you get
- Vaults searched across the covered protocols, filtered by minimum TVL and risk tier and sorted as you ask
- One vault opened up with its risk score on a 0-10 scale
- That score decomposed into risk vectors rather than reported as a single number
- Curator intelligence and protocol security history behind a vault
- Due diligence prompts and portfolio risk assessment on top of the vault data
Requirements
Nothing to install and no API key. Point a client at the hosted URL; Claude Code adds it with a single command.
Setup effort
One command — claude mcp add philidor --transport http https://mcp.philidor.io/api/mcp
USE CASES
01
Shortlisting vaults you would actually hold
Search with a minimum TVL and a risk tier, sorted the way you care about. What comes back is already filtered on the things that would otherwise disqualify a vault after you had read it.
02
Doing due diligence before you commit
Open the vault and read the score, the risk vectors underneath it, and the curator and protocol history behind them.
03
Comparing two vaults offering similar yield
Pull both and put the risk decompositions side by side. Where the headline yields match, the vectors are what separates them.
04
Checking the risk sitting in a portfolio you already have
Open each vault you hold and read its current score, so the assessment reflects where the vaults are now rather than when you entered them.
10 tools
Listed in project docs. Your client may show a different list.
get_vaultget_vault_risk_breakdowncompare_vaultsfind_safest_vaultsget_protocol_infoget_curator_infoget_market_overviewexplain_risk_scorelist_vaults_with_incidentsBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code
TERMINAL
claude mcp add philidor --transport http https://mcp.philidor.io/api/mcpHosted endpoint
ENDPOINT URL
https://mcp.philidor.io/api/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"philidor": {
"url": "https://mcp.philidor.io/api/mcp"
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"philidor": {
"serverUrl": "https://mcp.philidor.io/api/mcp"
}
}
}Any MCP client — Docker
ANY MCP CLIENT — DOCKER · TERMINAL
docker run -i --rm ghcr.io/philidor-labs/philidor-mcpAny MCP client — local build
ANY MCP CLIENT — LOCAL BUILD · TERMINAL
git clone https://github.com/Philidor-Labs/philidor-mcp.git
cd philidor-mcp
npm install
npm startCoding agents — skills
CODING AGENTS — SKILLS · TERMINAL
npx skills add philidor-labs/philidor-mcp
