check_loop_venue — Philidor DeFi Vault Risk Analytics MCP Tool Read-only
check_loop_venue
(check loop venue) is one of 14 tools on the
Philidor DeFi Vault Risk Analytics
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_loop_venue from your client
- Claude Code Philidor DeFi Vault Risk Analytics check_loop_venue run in your project directory
- Claude Desktop Philidor DeFi Vault Risk Analytics check_loop_venue ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Philidor DeFi Vault Risk Analytics check_loop_venue ~/.cursor/mcp.json
- VS Code Philidor DeFi Vault Risk Analytics check_loop_venue .vscode/mcp.json
- Zed Philidor DeFi Vault Risk Analytics check_loop_venue ~/.config/zed/settings.json
- Windsurf Philidor DeFi Vault Risk Analytics check_loop_venue ~/.codeium/windsurf/mcp_config.json
- Cline Philidor DeFi Vault Risk Analytics check_loop_venue ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Philidor DeFi Vault Risk Analytics check_loop_venue ~/.gemini/settings.json
- Grok Philidor DeFi Vault Risk Analytics check_loop_venue .mcp.json (in your project root)
- ChatGPT Philidor DeFi Vault Risk Analytics check_loop_venue Settings → Connectors → Advanced → Developer mode
- Claude.ai Philidor DeFi Vault Risk Analytics check_loop_venue Settings → Connectors → Add custom connector
- LangChain Philidor DeFi Vault Risk Analytics check_loop_venue pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http defi-vaults https://mcp.philidor.io/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.