ENS Resolver API
Resolve ENS human-readable names to Ethereum addresses and reverse lookups from your agent while building wallet, tipping, or Web3 features.
Overview
io.github.Br0ski777/ens-resolver is a MCP server for the Build phase that forward- and reverse-resolves ENS names and Ethereum addresses via remote SSE with x402 micropayment.
What is this MCP server?
- Forward resolve ENS names to Ethereum addresses
- Reverse resolution from address back to ENS when available
- Remote SSE MCP at ens-resolver.api.klymax402.com
- x402 micropayment on resolver calls
- Manifest version 1.1.0 with GitHub repo ens-resolver-x402
- 1 remote SSE endpoint: ens-resolver.api.klymax402.com/mcp
- Forward and reverse ENS resolution per server description
What problem does it solve?
Agents guessing or hardcoding Ethereum addresses from ENS names introduces wrong-recipient bugs and slow manual RPC scripting.
Who is it for?
Indie builders shipping tipping, identity, or payout flows that display or settle to ENS names inside an MCP-assisted codebase.
Skip if: Products with no on-chain identity needs or teams that already centralize resolution in a audited backend service.
What do I get? / Deliverables
Your agent can query authoritative ENS resolution and reverse lookups through MCP while you implement Web3-facing features.
- Resolved Ethereum address for a given ENS name
- Reverse ENS name when resolvable from an address
Recommended MCP Servers
Journey fit
How it compares
ENS lookup MCP bridge, not a wallet, DEX, or smart-contract deployment skill.
Common Questions / FAQ
Who is io.github.Br0ski777/ens-resolver for?
Developers building Ethereum-connected apps who want Claude Code, Cursor, or Codex to resolve ENS names and addresses through MCP.
When should I use io.github.Br0ski777/ens-resolver?
Use it during build when you integrate payments, profiles, or contracts that reference ENS instead of raw hex addresses.
How do I add io.github.Br0ski777/ens-resolver to my agent?
Configure remote MCP SSE URL https://ens-resolver.api.klymax402.com/mcp in your client, enable x402 micropayment per the repo, then call resolver tools from agent workflows.