mcpField
E
Ens Resolver X402

Ens Resolver X402

Remote
github.comFinance0Updated 8w ago

About Ens Resolver X402

Ens Resolver X402 is an ENS lookup service for AI agents that resolves names to Ethereum addresses and addresses back to ENS names, including associated avatar URLs. Calls use x402 pay-per-call payments in USDC on Base.

Key features

  1. 01Forward and reverse ENS lookup
  2. 02Return associated avatar URLs
  3. 03JSON resolution results
  4. 04x402 pay-per-call in USDC on Base

Use cases

  1. 01Check an ENS recipient address before sending funds
  2. 02Look up the ENS name linked to an Ethereum address

MCP support

Exposes the `crypto_resolve_ens` tool through a remote MCP server. MCP clients can request forward or reverse ENS resolution.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://ens-resolver.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

ENS Resolver API

MCP Server x402 License: MIT

Resolve ENS names to ETH addresses and reverse -- avatar URLs included. Identity layer for agents. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "ens-resolver": {
      "url": "https://ens-resolver.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://ens-resolver.api.klymax402.com/api/resolve" \
  -H "Content-Type: application/json" \
  -d '{}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
crypto_resolve_ensPOST/api/resolve$0.005Resolve ENS name to Ethereum address or reverse-resolve address to ENS name
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.

Parameters

NameTypeRequiredDescription
namestringnoENS name to resolve (e.g. vitalik.eth)
addressstringnoEthereum address for reverse resolution (e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045)

Returns

  • address -- resolved Ethereum address (0x...)
  • ensName -- ENS name (e.g. vitalik.eth)
  • avatar -- avatar URL associated with the ENS name (if set)
  • resolvedDirection -- "forward" (name to address) or "reverse" (address to name)

Example response:

{"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","ensName":"vitalik.eth","avatar":"https://...","resolvedDirection":"forward"}

When to use: sending funds to an ENS name to verify the correct address. Essential for identity resolution and human-readable wallet lookup.

Not for: wallet balances (use wallet_get_portfolio), token safety (use token_check_safety), NFT metadata (use crypto_get_nft_metadata).

Example agent prompts

  • "Resolve an ENS name to an Ethereum address, or reverse-resolve an address to its ENS name"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.