Global AI chat room · 18 online now Join now
E
MCP SERVER Listed

ENS Resolver — Name ↔ Address + Avatar

ENS name resolution API for AI agents. Resolve ENS names (vitalik.eth) to Ethereum addresses and reverse-resolve addresses to ENS names. Includes avatar URLs and text records. Tools: crypto_resolve_ens. Use this for displaying human-readable names, identity verification, or building wallet UIs. The identity layer every crypto agent needs. IMPORTANT: For wallet balance lookup, use wallet_get_portfolio instead. Returns: {address, name, avatar, records}. No API key required — x402 micropayment $0.002/call on Base L2.

Open ecosystemRemote MCPmcpsmithery
View GitHub
01 / SERVER DETAIL

Server detail

ENS name resolution API for AI agents. Resolve ENS names (vitalik.eth) to Ethereum addresses and reverse-resolve addresses to ENS names. Includes avatar URLs and text records. Tools: crypto_resolve_ens. Use this for displaying human-readable names, identity verification, or building wallet UIs. The identity layer every crypto agent needs. IMPORTANT: For wallet balance lookup, use wallet_get_portfolio instead. Returns: {address, name, avatar, records}. No API key required — x402 micropayment $0.002/call on Base L2.

An MCP server that exposes ENS Resolver — Name ↔ Address + Avatar capabilities to MCP-compatible AI clients.

CapabilitiesmcpsmitheryMCPOpen source
ProtocolModel Context Protocol
Developer ecosystemOpen ecosystem
LicenseMIT / check source
SourceGitHub
COLLECTIONS

Collections featuring this MCP

Popular MCP2026.03.30Listed
My MCP2026.03.31Listed
Genie2026.03.30Listed
02 / TOOL TESTING

Tool testing

AVAILABLE TOOL

ens-resolver---name---address---avatar

Callable

Call the MCP capabilities provided by ENS Resolver — Name ↔ Address + Avatar and return a structured result.

PARAMETERS
inputPass arguments according to the server tool schema.
Tip: the tool may truncate responses. Use pagination parameters such as start_index to read long content in chunks.
03 / SERVICE CONFIGURATION

Connection modes

Remote
{
  "mcpServers": {
    "ENS Resolver — Name ↔ Address + Avatar": {
      "url": "Generated by the provider after deployment"
    }
  }
}

The Remote endpoint is generated by the provider after deployment; this page does not fabricate an unusable endpoint.

03 / WORKFLOW

How to use

  1. 01
    Step 1

    Review server capabilities and permission scope.

  2. 02
    Step 2

    Copy the install command or JSON configuration.

  3. 03
    Step 3

    Run a small connection test in your client.

  4. 04
    Step 4

    Adopt it long term only after reviewing access and maintenance.

04 / DISCUSSIONS

Discussions

Use this space to keep checking source information, usage experience and maintenance status.

Open source page
Email