ENS Resolver API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

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

VerifiedSSEWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

Remote MCP server that resolves ENS names to Ethereum addresses and back, with avatar URLs, paid per call via x402 USDC micropayments.

What you can do
Resolve an ENS name to its Ethereum address, or reverse-resolve an address to its ENS name, returning address, ensName, avatar and resolution direction as JSON.
When to use it
Useful when an assistant needs to check the address behind an ENS name before sending funds, or turn a wallet address into a human-readable name for identity lookup.
Requirements
A remote SSE endpoint; no API key, signup or environment variables. Each call is paid in USDC on Base L2 through the x402 protocol, so an x402-aware client with a funded wallet is needed to complete the payment challenge.
Before you install
Every call costs money (listed at $0.005 per resolve) in USDC on Base, so an agent can spend funds automatically. Payment is handled by third-party facilitators (Coinbase CDP, PayAI), and the wallet used for signing should be treated as a spending credential.

Installation

In SourceWeft

  1. Open ENS Resolver API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fens-resolver/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

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.):

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

Quickstart -- HTTP (x402)

bash
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:

json
{"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

Source: README.md at commit e6ffcb4

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts