mcpbeat Sign in

Philidor DeFi Vault Risk Analytics MCP Server

answering

Philidor DeFi Vault Risk Analytics is answering right now. Last checked 13 min ago. It exposes 14 tools. Last commit 2 Mar 2026.

Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed.

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
14
Tools
read from the server
449 ms
Response time
average over 24h
5
Stars
last commit 2 Mar 2026

What changed 22

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 August 2026. No other catalogue keeps this.

12 Sep 5 tools changed the parameters they ask for get_market, get_market_events, get_protocol_info and 2 more
12 Sep 3 tool descriptions were rewritten get_market, get_market_events, list_markets
12 Sep a tool appeared check_loop_venue
3 Sep 3 tools changed the parameters they ask for get_protocol_info, list_markets, search_vaults
3 Sep a tool description was rewritten list_markets
28 Aug 6 tools changed the parameters they ask for compare_vaults, find_safest_vaults, get_vault and 3 more
25 Aug a tool appeared get_market_events
23 Aug 2 tools appeared get_market, list_markets

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command bin/cli.mjs:9
execFileSync(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add defi-vaults --transport http https://mcp.philidor.io/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "defi-vaults": {
      "url": "https://mcp.philidor.io/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.defi-vaults]
url = "https://mcp.philidor.io/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "defi-vaults": {
      "url": "https://mcp.philidor.io/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "defi-vaults": {
      "url": "https://mcp.philidor.io/api/mcp"
    }
  }
}

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

market
get_market
Get one lending market with every reserve it contains: supplied, supply APR, borrowed, borrow APR, utilization and risk tier per reserve. Spoke ids look like aave-v4-10-etherfi-cash. Aave V4 hub parents (aave-v4-1-hub-global-dollar) are composed from the spokes that share that hub; /v1/markets does not serve those ids.
get_market_events
Published risk events for ONE lending market: incidents, bad debt, liquidation cascades (e.g. mass liquidations on a Morpho Blue market). Market ids look like morpho-v1-1-pt-reusd-10dec2026-usdc-91-5. Aave V4 hub ids (aave-v4-1-hub-global-dollar) union the spoke feeds. Not platform stats (get_market_overview) and not the market data itself (get_market).
get_market_overview
Get a high-level overview of the DeFi vault market: total TVL, vault count, risk distribution, and TVL by protocol.
vault
get_vault
Get detailed information about a specific DeFi vault including risk breakdown, recent events, and historical snapshots. Lookup by ID or by network + address.
get_vault_risk_breakdown
Get a detailed breakdown of a vault's risk vectors: Asset Composition, Platform and Strategy, Control and Governance, and History scores with sub-metrics.
vaults
list_vaults_with_incidents
List all vaults that had a recent critical incident (last 365 days). Critical = severity Critical or incident_severity major. Results are sorted by TVL descending, then by time since event ascending (most recent first).
search_vaults
Search and filter DeFi vaults by chain, protocol, asset, risk tier, TVL, and more. Returns a paginated list with risk scores and APR.
compare
compare_vaults
Compare 2-3 DeFi vaults side-by-side on TVL, APR, risk score, risk tier, audited status, and more.
curator
get_curator_info
Get detailed information about a vault curator including their managed vaults, TVL, chain distribution, and performance.
explain
explain_risk_score
Explain what a Philidor risk score means, including the tier (Prime/Core/Edge), how it is calculated, and what the thresholds are.
loop
check_loop_venue
Underwrite a collateral/debt loop on ONE lending market: score, tier, utilization, borrow APR, deposit status, and recent incidents for both reserves. Does not compute health factor and does not prepare txs. Call this before a protocol MCP preview_action / prepare_action. If you do not have a market id, call list_markets first (Aave V4: protocol=aave, version=v4). Examples: aave-v4-1-main, aave-v4-10-etherfi-cash, aave-v4-1-hub-global-dollar.
markets
list_markets
List lending markets: the market a depositor actually picks (Aave/Spark pool, Aave V4 spoke, Compound Comet, Morpho Blue pair, or Kamino K-Lend market). Aave V4 spokes that share a liquidity hub are grouped under a composed parent (aave-v4-1-hub-global-dollar). The API still keys each market on the spoke. NOTE: this is not `get_market_overview`, which returns platform-wide totals across all vaults.
protocol
get_protocol_info
Get detailed information about a DeFi protocol including TVL, vault count, versions, auditors, and security incidents.
safest
find_safest_vaults
Find the highest risk-scored DeFi vaults, optionally filtered by asset, chain, or minimum TVL. Returns the top 10 audited vaults sorted by Philidor risk score (higher = lower assessed risk; scores are not a safety guarantee).

Endpoints

URLTransportStateLatencyChecked
https://mcp.philidor.io/api/mcp streamable-http answering 134 ms 13 min ago

Alternatives to Philidor DeFi Vault Risk Analytics

same job, measured the same way
Sui Analytics
by 0xfreak0

Read-only Sui analytics: 68 tools, protocol-aware tx decoding, no API keys or wallet.

1 206 installs/wk local only
C
Tiktok
by scraptik

Unofficial TikTok API & scraper: creator analytics, video data, comments, search. x402, no API key.

19 tools answering
Resell Pro
by flipradar

Observed Vinted market analytics: compare brands, research niches, and discover trends via OAuth.

answering
Inbio
by www-in-bio

Official in.bio MCP server: shorten URLs, styled QR codes, and click analytics. No API key needed.

12 tools answering
Github Analytics MCP Server
by thenextgennexus

Get GitHub repository stats, search repos, analyze languages, and compare projects

20 installs/wk local only
Portkey Admin MCP
by s-b-e-n-s-o-n

Full Portkey Admin API MCP server — configs, prompts, keys, analytics, and more.

438 installs/wk local only
O
DeFi Protocol Data
by memoryapi

DeFi protocol data: TVL, yield pools, and cross-chain analytics

3 tools answering
Kontur Focus MCP
by theyahia

MCP server for Kontur.Focus API — company search, brief reports, financial analytics, counterparty

39 installs/wk local only

Philidor DeFi Vault Risk Analytics — questions

Answers built from our own checks of this server.

What can Philidor DeFi Vault Risk Analytics do?
It exposes 14 tools, read directly from the server on our last check. Among them: check_loop_venue, compare_vaults, explain_risk_score, find_safest_vaults, get_curator_info, get_market and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Philidor DeFi Vault Risk Analytics mostly used for?
Its tools cluster around market, vault and vaults. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Philidor DeFi Vault Risk Analytics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 449 ms. The bar chart above shows every period we have measured.
How do I connect Philidor DeFi Vault Risk Analytics?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Philidor DeFi Vault Risk Analytics need an API key?
No. Philidor DeFi Vault Risk Analytics completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Philidor DeFi Vault Risk Analytics?
It answers our handshake in 449 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Philidor DeFi Vault Risk Analytics open source?
Yes — it is published under the MIT licence, written in TypeScript, 5 stars on GitHub and 2 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.