monitor_crossing_candidates — MEV Intelligence MCP Tool
monitor_crossing_candidates
(monitor crossing candidates) is one of 10 tools on the
MEV Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call monitor_crossing_candidates from your client
- Claude Code MEV Intelligence monitor_crossing_candidates run in your project directory
- Claude Desktop MEV Intelligence monitor_crossing_candidates ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MEV Intelligence monitor_crossing_candidates ~/.cursor/mcp.json
- VS Code MEV Intelligence monitor_crossing_candidates .vscode/mcp.json
- Zed MEV Intelligence monitor_crossing_candidates ~/.config/zed/settings.json
- Windsurf MEV Intelligence monitor_crossing_candidates ~/.codeium/windsurf/mcp_config.json
- Cline MEV Intelligence monitor_crossing_candidates ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MEV Intelligence monitor_crossing_candidates ~/.gemini/settings.json
- Grok MEV Intelligence monitor_crossing_candidates .mcp.json (in your project root)
- ChatGPT MEV Intelligence monitor_crossing_candidates Settings → Connectors → Advanced → Developer mode
- Claude.ai MEV Intelligence monitor_crossing_candidates Settings → Connectors → Add custom connector
- LangChain MEV Intelligence monitor_crossing_candidates pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http intelligence https://mev.advalorem.io/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.