Philidor MCP Server

MCP server for DeFi vault risk analytics — search vaults, compare risks, analyze protocols using the Vector Risk Framework

Remote serverstreamable-http

What is the Philidor MCP MCP server?

Philidor MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Philidor MCP directly instead of describing what you should do. MCP server for DeFi vault risk analytics — search vaults, compare risks, analyze protocols using the Vector Risk Framework.

What you get

Search 700+ DeFi vaults across Morpho, Aave, Yearn, Beefy, and Spark. Compare risk scores, analyze protocols, run due diligence — all through natural language.

What the assistant can call

Once Philidor MCP is connected, these are the calls the assistant has available:

  • Cursor — The Cursor tool exposed by this server
  • Windsurf — The Windsurf tool exposed by this server
  • search_vaults — Search and filter DeFi vaults by chain, protocol, asset, risk tier, TVL, and more
  • get_vault — Get detailed information about a specific vault including risk breakdown, recent events, and historical snapshots. Lookup by id or by network +
  • get_vault_risk_breakdown — Detailed breakdown of a vault's three risk vectors with sub-metrics: asset quality, platform code maturity, and governance controls. Returns
  • compare_vaults — Side-by-side comparison of 2–3 vaults on TVL, APR, risk score, risk tier, and audit status
  • find_safest_vaults — Find the top 10 audited, high-confidence vaults sorted by risk score
  • get_protocol_info — Protocol details including TVL, vault count, versions, auditors, bug bounties, and security incidents
  • get_curator_info — Curator details including managed vaults, TVL, chain distribution, and performance metrics
  • get_market_overview — High-level DeFi vault market statistics: total TVL, vault count, risk distribution, and TVL by protocol. No parameters required
  • explain_risk_score — Explain what a specific risk score means, including the tier, calculation method, and thresholds
  • list_vaults_with_incidents — List all vaults that had a recent critical incident (last 365 days). Sorted by TVL descending, then by recency. No parameters required

Configuration and credentials

You will need one environment variable: PHILIDOR_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Philidor MCP's toolset — Cursor, Windsurf, search_vaults and 9 more — is a fair guide to whether it matches your workflow. It is maintained by philidor-labs; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Philidor MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the philidor mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.
WindsurfThe Windsurf tool exposed by this server.
search_vaultsSearch and filter DeFi vaults by chain, protocol, asset, risk tier, TVL, and more.
get_vaultGet detailed information about a specific vault including risk breakdown, recent events, and historical snapshots. Lookup by id or by network + address.
get_vault_risk_breakdownDetailed breakdown of a vault's three risk vectors with sub-metrics: asset quality, platform code maturity, and governance controls. Returns dimension-level scores, caps, hard-fail flags, and overrides.
compare_vaultsSide-by-side comparison of 2–3 vaults on TVL, APR, risk score, risk tier, and audit status.
find_safest_vaultsFind the top 10 audited, high-confidence vaults sorted by risk score.
get_protocol_infoProtocol details including TVL, vault count, versions, auditors, bug bounties, and security incidents.
get_curator_infoCurator details including managed vaults, TVL, chain distribution, and performance metrics.
get_market_overviewHigh-level DeFi vault market statistics: total TVL, vault count, risk distribution, and TVL by protocol. No parameters required.
explain_risk_scoreExplain what a specific risk score means, including the tier, calculation method, and thresholds.
list_vaults_with_incidentsList all vaults that had a recent critical incident (last 365 days). Sorted by TVL descending, then by recency. No parameters required.

How to install the Philidor MCP MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PHILIDOR_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Philidor MCP to Cursor.
  • Use Philidor MCP to Windsurf.
  • Use Philidor MCP to search vaults.

Frequently asked questions

It connects Philidor MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 12 tools (Cursor, Windsurf, search_vaults, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Philidor MCP directly.