mcpbeat

ENS Resolver API MCP Server

io.github.Br0ski777/ens-resolver
answering

ENS Resolver API is answering right now. Last checked 3 min ago. It exposes 1 tools. Last commit 19 Jul 2026.

Resolve ENS names to Ethereum addresses and reverse. x402 micropayment.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
31 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add ens-resolver --transport http https://ens-resolver.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ens-resolver": {
      "url": "https://ens-resolver.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ens-resolver]
url = "https://ens-resolver.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ens-resolver": {
      "url": "https://ens-resolver.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ens-resolver": {
      "url": "https://ens-resolver.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

crypto
crypto_resolve_ens
Use this when you need to resolve an ENS name to an Ethereum address, or reverse-resolve an address to its ENS name. Returns resolution data in JSON. 1. address: resolved Ethereum address (0x...) 2. ensName: ENS name (e.g. vitalik.eth) 3. avatar: avatar URL associated with the ENS name (if set) 4. resolvedDirection: "forward" (name to address) or "reverse" (address to name) Example output: {"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","ensName":"vitalik.eth","avatar":"https://...","resolvedDirection":"forward"} Use this BEFORE sending funds to an ENS name to verify the correct address. Essential for identity resolution and human-readable wallet lookup. Do NOT use for wallet balances -- use wallet_get_portfolio instead. Do NOT use for token safety -- use token_check_safety instead. Do NOT use for NFT metadata -- use crypto_get_nft_metadata instead.

Endpoints

URLTransportStateLatencyChecked
https://ens-resolver.api.klymax402.com/mcp sse answering 28 ms 3 min ago

ENS Resolver API — questions

Answers built from our own checks of this server.

What can ENS Resolver API do?
It exposes 1 tools, read directly from the server on our last check. Among them: crypto_resolve_ens. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ENS Resolver API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 31 ms. The bar chart above shows every period we have measured.
How do I connect ENS Resolver API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ENS Resolver API need an API key?
No. ENS Resolver API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ENS Resolver API?
It answers our handshake in 31 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is ENS Resolver API open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.