ens_resolve — APEX EVM Reads MCP Tool
ens_resolve
(ens resolve) is one of 17 tools on the
APEX EVM Reads
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ens_resolve from your client
- Claude Code APEX EVM Reads ens_resolve run in your project directory
- Claude Desktop APEX EVM Reads ens_resolve ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor APEX EVM Reads ens_resolve ~/.cursor/mcp.json
- VS Code APEX EVM Reads ens_resolve .vscode/mcp.json
- Zed APEX EVM Reads ens_resolve ~/.config/zed/settings.json
- Windsurf APEX EVM Reads ens_resolve ~/.codeium/windsurf/mcp_config.json
- Cline APEX EVM Reads ens_resolve ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI APEX EVM Reads ens_resolve ~/.gemini/settings.json
- Grok APEX EVM Reads ens_resolve .mcp.json (in your project root)
- ChatGPT APEX EVM Reads ens_resolve Settings → Connectors → Advanced → Developer mode
- Claude.ai APEX EVM Reads ens_resolve Settings → Connectors → Add custom connector
- LangChain APEX EVM Reads ens_resolve pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http apex-evm https://apexfaucet.xyz/api/mcp/evmOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 13 October 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.