Philidor DeFi Vault Risk Analytics
REMOTE · MCP.PHILIDOR.IO · SCANNED SEP 26
Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2163 tokens (~127/item across 17 items; 14 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management95
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Philidor DeFi Vault Risk Analytics MCP server?
Philidor DeFi Vault Risk Analytics is a hosted endpoint at https://mcp.philidor.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.philidor.io
claude mcp add --transport http io-philidor-defi-vaults 'https://mcp.philidor.io/api/mcp'
{
"mcpServers": {
"io-philidor-defi-vaults": {
"url": "https://mcp.philidor.io/api/mcp"
}
}
} {
"servers": {
"io-philidor-defi-vaults": {
"type": "http",
"url": "https://mcp.philidor.io/api/mcp"
}
}
} [mcp_servers.io-philidor-defi-vaults] url = "https://mcp.philidor.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-philidor-defi-vaults": {
"type": "remote",
"url": "https://mcp.philidor.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-philidor-defi-vaults --url 'https://mcp.philidor.io/api/mcp' --transport streamable-http
mcp_servers:
io-philidor-defi-vaults:
url: "https://mcp.philidor.io/api/mcp" {
"McpServers": {
"io-philidor-defi-vaults": {
"Transport": "http",
"Url": "https://mcp.philidor.io/api/mcp"
}
}
} assistant mcp add io-philidor-defi-vaults -t streamable-http -u 'https://mcp.philidor.io/api/mcp'
{
"mcpServers": {
"io-philidor-defi-vaults": {
"type": "http",
"url": "https://mcp.philidor.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −1
- Stability: pass → fail ▼ security
- 13 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_market” rewrote its description, which is the text the model reads security
- Tool “get_market_events” rewrote its description, which is the text the model reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New prompt “review_loop_venue” functional
- New tool “check_loop_venue” functional
- “search_vaults” added an optional parameter “protocolVersion” cosmetic
- “get_market” reworded the description of “marketId” cosmetic
- “get_market_events” reworded the description of “marketId” cosmetic
- “get_protocol_info” reworded the description of “protocolId” cosmetic
- “list_markets” reworded the description of “protocol” cosmetic
- “list_markets” reworded the description of “version” cosmetic
- “search_vaults” reworded the description of “protocol” cosmetic
- 4 Sept 26 +1
- Stability: 0.97 → pass security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- “get_protocol_info” reworded the description of “protocolId” cosmetic
- “list_markets” reworded the description of “protocol” cosmetic
- “list_markets” reworded the description of “version” cosmetic
- “search_vaults” reworded the description of “protocol” cosmetic
- 3 Sept 26 −1
- Stability: pass → 0.97 functional
- 29 Aug 26 0
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- “list_markets” changed the type of “chain”: number → number|string ▼ functional
- “find_safest_vaults” reworded the description of “chain” cosmetic
- “get_vault” reworded the description of “address” cosmetic
- “get_vault” reworded the description of “network” cosmetic
- “get_vault_risk_breakdown” reworded the description of “address” cosmetic
- “get_vault_risk_breakdown” reworded the description of “network” cosmetic
- “list_markets” reworded the description of “chain” cosmetic
- “list_markets” reworded the description of “protocol” cosmetic
- “search_vaults” reworded the description of “chain” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://mcp.philidor.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=philidor.io | CN=WE1,O=Google Trust Services,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ea4d426271325c5e0ef63d9373a1fcb7 |
| SANs: philidor.io, mcp.philidor.io, *.mcp.philidor.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.philidor.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| philidor.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.philidor.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.philidor.io/api/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_loop_venue ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| collateral | string | yes | Collateral asset symbol you will post (e.g. weETH, WETH, cbBTC). |
| debt | string | yes | Debt asset symbol you will borrow (e.g. USDC, USDT, GHO). |
| marketId | string | yes | Market id from list_markets. Spoke example: aave-v4-1-main. Hub example: aave-v4-1-hub-global-dollar. |
No output schema declared.
No examples provided.
compare_vaults ~58
Compare 2-3 DeFi vaults side-by-side on TVL, APR, risk score, risk tier, audited status, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| vaults | array | yes | Array of 2-3 vaults to compare |
No output schema declared.
No examples provided.
explain_risk_score ~55
Explain what a Philidor risk score means, including the tier (Prime/Core/Edge), how it is calculated, and what the thresholds are.
| Name | Type | Req | Description |
|---|---|---|---|
| score | number | yes | Risk score (0-10) to explain |
No output schema declared.
No examples provided.
find_safest_vaults ~125
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).
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Filter by asset symbol (e.g. USDC, WETH) |
| chain | string | – | Filter by chain name or slug (e.g. Ethereum, Base, Arbitrum, Solana) |
| minTvl | number | – | Minimum TVL in USD |
No output schema declared.
No examples provided.
get_curator_info ~43
Get detailed information about a vault curator including their managed vaults, TVL, chain distribution, and performance.
| Name | Type | Req | Description |
|---|---|---|---|
| curatorId | string | yes | Curator ID |
No output schema declared.
No examples provided.
get_market ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| marketId | string | yes | Market id from list_markets. Spoke example: aave-v4-10-etherfi-cash. Hub example: aave-v4-1-hub-global-dollar. |
No output schema declared.
No examples provided.
get_market_events ~152
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max events (default 20) |
| marketId | string | yes | Market id from list_markets. Spoke or composed hub parent (aave-v4-1-hub-global-dollar). |
No output schema declared.
No examples provided.
get_market_overview ~38
Get a high-level overview of the DeFi vault market: total TVL, vault count, risk distribution, and TVL by protocol.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_protocol_info ~88
Get detailed information about a DeFi protocol including TVL, vault count, versions, auditors, and security incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| protocolId | string | yes | Protocol ID: aave, morpho, spark, compound, yearn, beefy, uniswap, nest, maple, kamino. Aave V4 is listed under aave (aave-v4 is accepted as an alias). |
No output schema declared.
No examples provided.
get_vault ~133
Get detailed information about a specific DeFi vault including risk breakdown, recent events, and historical snapshots. Lookup by ID or by network + address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Vault address in the chain's namespace: 0x-hex on EVM chains, base58 (case-sensitive) on Solana |
| id | string | – | Vault ID (e.g. morpho-1-0x...) |
| network | string | – | Network slug from the chain registry (e.g. ethereum, base, arbitrum, solana). /v1/chains lists slugs for chains with active vaults. |
No output schema declared.
No examples provided.
get_vault_risk_breakdown ~118
Get a detailed breakdown of a vault's risk vectors: Asset Composition, Platform and Strategy, Control and Governance, and History scores with sub-metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Vault address in the chain's namespace: 0x-hex on EVM chains, base58 (case-sensitive) on Solana |
| network | string | yes | Network slug from the chain registry (e.g. ethereum, base, arbitrum, solana). /v1/chains lists slugs for chains with active vaults. |
No output schema declared.
No examples provided.
list_markets ~257
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | number|string | – | Filter by chain: integer chain id (e.g. 1, 8453) or slug (e.g. ethereum, solana) |
| limit | number | – | Results per page (1-100, default 20) |
| protocol | string | – | Filter by protocol id: aave, spark, compound, morpho, kamino. Aave V4 is protocol=aave plus version=v4 (aave-v4 is accepted as an alias). |
| sortBy | string | – | Sort field (default total_supplied_usd) |
| version | string | – | Filter by protocol version: v3, v4, or klend. Use version=v4 with protocol=aave. |
No output schema declared.
No examples provided.
list_vaults_with_incidents ~58
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_vaults ~379
Search and filter DeFi vaults by chain, protocol, asset, risk tier, TVL, and more. Returns a paginated list with risk scores and APR.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Filter by asset symbol (e.g. USDC, WETH) |
| chain | string | – | Filter by chain name or slug (e.g. Ethereum, Base, Arbitrum, Solana) |
| depositable | boolean | – | Filter by current ability to accept new deposits. When true, vaults whose depositability is not yet indexed are still included; when false, only vaults whose maxDeposit on-chain is zero (caps reached… |
| limit | number | – | Max results (default 10, max 50) |
| minTvl | number | – | Minimum TVL in USD |
| protocol | string | – | Filter by protocol ID: aave, morpho, spark, compound, yearn, beefy, uniswap, nest, maple, kamino. Aave V4 is protocol=aave plus protocolVersion=v4 (aave-v4 is accepted as an alias). |
| protocolVersion | string | – | Filter by protocol generation: v3, v4, v3-lido, v3-horizon, klend, kvault. Required to isolate Aave V4 (protocol=aave, protocolVersion=v4). Vaults list this as protocol_version. |
| query | string | – | Search by vault name, symbol, asset, protocol, or curator |
| riskTier | string | – | Filter by risk tier: Prime, Core, or Edge |
| sortBy | string | – | Sort field: tvl_usd, apr_net, name, last_synced_at |
| sortOrder | string | – | Sort order: asc or desc |
No output schema declared.
No examples provided.
What is the Philidor DeFi Vault Risk Analytics MCP server?
Philidor DeFi Vault Risk Analytics is an MCP server listed in the public MCP registry as io.philidor/defi-vaults. Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed. This page covers its hosted endpoint (https://mcp.philidor.io/api/mcp).
Is the Philidor DeFi Vault Risk Analytics MCP server safe to use?
Philidor DeFi Vault Risk Analytics scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Philidor DeFi Vault Risk Analytics MCP server expose?
Philidor DeFi Vault Risk Analytics exposes 14 tools: search_vaults, get_vault, get_vault_risk_breakdown, list_markets, get_market, and 9 more. Their descriptions and schemas cost roughly 1,856 tokens of context every time the server is loaded.
Does the Philidor DeFi Vault Risk Analytics MCP server require authentication?
No. We connected to Philidor DeFi Vault Risk Analytics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Philidor DeFi Vault Risk Analytics MCP server still maintained?
Philidor DeFi Vault Risk Analytics is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.