resolution_diff — Alchemy Eth MCP Tool
resolution_diff
(resolution diff) is one of 45 tools on the
Alchemy Eth
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 Alchemy Eth resolution_diff run in your project directory
- Claude Desktop Alchemy Eth resolution_diff ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Alchemy Eth resolution_diff ~/.cursor/mcp.json
- VS Code Alchemy Eth resolution_diff .vscode/mcp.json
- Zed Alchemy Eth resolution_diff ~/.config/zed/settings.json
- Windsurf Alchemy Eth resolution_diff ~/.codeium/windsurf/mcp_config.json
- Cline Alchemy Eth resolution_diff ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Alchemy Eth resolution_diff ~/.gemini/settings.json
- Grok Alchemy Eth resolution_diff .mcp.json (in your project root)
- ChatGPT Alchemy Eth resolution_diff Settings → Connectors → Advanced → Developer mode
- Claude.ai Alchemy Eth resolution_diff Settings → Connectors → Add custom connector
- LangChain Alchemy Eth resolution_diff pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http alchemy-eth https://gateway.pipeworx.io/alchemy-eth/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
- eth_call
- token_balances
- token_metadata
- token_allowance
- nfts_owned
- nft_metadata
- nfts_for_collection
- nft_owners
- asset_transfers
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.