Philidor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PHILIDOR_API_URL | No | Custom API endpoint for the Philidor API. The server connects to the public Philidor API by default. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_vaultsA | Search and filter DeFi vaults by chain, protocol, asset, risk tier, TVL, and more. Returns a paginated list with risk scores and APR. |
| get_vaultA | 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_breakdownC | Get a detailed breakdown of a vault's risk vectors: Asset Composition, Platform Code, and Governance scores with sub-metrics. |
| compare_vaultsA | Compare 2-3 DeFi vaults side-by-side on TVL, APR, risk score, risk tier, audited status, and more. |
| find_safest_vaultsA | Find the safest (highest risk-scored) DeFi vaults, optionally filtered by asset, chain, or minimum TVL. Returns top 10 audited, high-confidence vaults sorted by risk score. |
| get_protocol_infoB | Get detailed information about a DeFi protocol including TVL, vault count, versions, auditors, and security incidents. |
| get_curator_infoA | Get detailed information about a vault curator including their managed vaults, TVL, chain distribution, and performance. |
| get_market_overviewA | Get a high-level overview of the DeFi vault market: total TVL, vault count, risk distribution, and TVL by protocol. |
| explain_risk_scoreA | Explain what a Philidor risk score means, including the tier (Prime/Core/Edge), how it is calculated, and what the thresholds are. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| vault_due_diligence | Generate a comprehensive due diligence report for a specific DeFi vault. |
| portfolio_risk_assessment | Analyze portfolio-level risk across multiple vault positions. |
| defi_yield_comparison | Compare DeFi yield opportunities across vaults, filtered by asset, chain, or risk tier. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| methodology | The Vector Risk Framework v2.0 methodology used by Philidor to score DeFi vault risk. |
| supported-chains | List of blockchain networks supported by Philidor with vault counts and TVL. |
| supported-protocols | List of DeFi protocols tracked by Philidor with vault counts and TVL. |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the DeFi vault domain, with no overlap that could cause confusion. For example, 'get_vault' retrieves detailed vault information, while 'get_vault_risk_breakdown' focuses specifically on risk metrics, and 'search_vaults' handles filtering and listing.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'compare_vaults', 'explain_risk_score', and 'get_vault_risk_breakdown'. This predictable naming convention makes the tool set easy to navigate and understand.
With 9 tools, the server is well-scoped for analyzing DeFi vaults, covering key aspects like risk assessment, market overview, and vault details. Each tool serves a unique function without redundancy, making the count appropriate for the domain.
The tool set provides comprehensive coverage for DeFi vault analysis, including CRUD-like operations (e.g., get, search, compare), risk explanation, market insights, and curator/protocol details. There are no obvious gaps that would hinder an agent from performing essential tasks in this domain.