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