resolution_diff — Esma Firds MCP Tool
resolution_diff
(resolution diff) is one of 39 tools on the
Esma Firds
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolution_diff from your client
- Claude Code Esma Firds resolution_diff run in your project directory
- Claude Desktop Esma Firds resolution_diff ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Esma Firds resolution_diff ~/.cursor/mcp.json
- VS Code Esma Firds resolution_diff .vscode/mcp.json
- Zed Esma Firds resolution_diff ~/.config/zed/settings.json
- Windsurf Esma Firds resolution_diff ~/.codeium/windsurf/mcp_config.json
- Cline Esma Firds resolution_diff ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Esma Firds resolution_diff ~/.gemini/settings.json
- Grok Esma Firds resolution_diff .mcp.json (in your project root)
- ChatGPT Esma Firds resolution_diff Settings → Connectors → Advanced → Developer mode
- Claude.ai Esma Firds resolution_diff Settings → Connectors → Add custom connector
- LangChain Esma Firds resolution_diff pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http esma-firds https://gateway.pipeworx.io/esma-firds/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- firds_lookup
- firds_search_by_issuer
- esma_check_firm_authorisation
This list was read from the server itself, by connecting to it and calling tools/list on 26 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.