Browse all documentation
Documentation home
Get started
Platform overviewConnect a walletSafety, simulation, and signing
Find names
Expiry ExplorerAI domain searchDiscover and collectionsBulk searchENS lookup and domain details
Trade names
Browse the marketplaceBuy a listed nameList a name for saleBulk list namesActivity and collectionsMake, manage, and accept offersLeaderboard and market analyticsLive market pulse and network activity
Manage names
Portfolio dashboardPublic Portfolio 2.0Renewals and gas planningBulk edit records and resolversTransfers and subnamesSet a primary ENS nameWatchlist and notificationsLive calendar subscriptionsSaved-search monitorsUnified action inboxPublic profiles and share cards
Agent platform
Agent platform overviewLaunch an ENS-native agentAgent directory and profilesCapability health checksIntent routingPolicy-bound agent sessionsAgent jobs, quotes, and escrow evidenceCreate and control agent fleetsControl-plane canary evidence
Developers
MCP quickstartComplete MCP tool catalogueDeveloper accounts, sandbox, quotas, and Base subscriptionsUnsigned transaction plansAgent identity standardsPublic APIs and manifestsMarketplace integration
Reference
ENSv2 public betaENS lifecycle and status meaningsFees and displayed totalsTroubleshooting
Developers · 1 of 7

MCP quickstart

Connect an AI client to the public ENS.Tools MCP endpoint.

betaserver 3.0 · 79 MCP tools · platform contract v1Verified 2026-07-29Owner: ENS.Tools Developer Platform
Open this feature

Both MCP profiles are public, stateless Streamable HTTP. Start with the stable 25-tool lite profile for lower context use, or use the unchanged full profile when maximum compatibility matters.

Lite endpoint: https://ens.tools/mcp-lite — 25 workflow tools plus search_tools.
Full endpoint: https://ens.tools/mcp — the complete canonical catalogue.
Current protocol revision: 2025-11-25.
Compatible revisions: 2025-06-18, 2025-03-26, and 2024-11-05.
Each runtime tools/list is deterministic; search_tools never mutates the lite list.
No server-initiated SSE stream or issued session ID.
Production contract

Before you run this workflow

Networks

  • Ethereum mainnet for onchain plans
  • HTTPS for MCP and public APIs

Prerequisites

  • JSON-RPC 2.0 client for MCP
  • Read the live platform contract and tool schemas at runtime

Wallet permissions

  • MCP never receives private keys
  • Prepared writes must be reviewed, signed, and broadcast by a separate wallet

Expected result

  • Structured JSON data or an unsigned plan with chain, target, calldata, value, and safety metadata

Errors and recovery

  • Call tools/list again after schema errors
  • Back off after rate limits
  • Simulate immediately before signing
Workflow

How to use it

  1. 1

    Choose a profile

    Use lite for common workflows and lower context use. Choose full when the client must call any tool directly.

  2. 2

    Initialize

    Negotiate a supported protocol revision and identify your client.

  3. 3

    Discover tools

    Call tools/list at runtime. On lite, search_tools returns matching full-catalogue schemas and the full endpoint for non-lite calls.

  4. 4

    Start with a read

    Try lookup_domain or get_agent_context before preparing any action.

Examples

Claude Code · Lite
claude mcp add ens-tools-lite --transport http https://ens.tools/mcp-lite
Claude Code · Full
claude mcp add ens-tools --transport http https://ens.tools/mcp
JSON configuration
{
  "mcpServers": {
    "ens-tools-lite": {
      "url": "https://ens.tools/mcp-lite",
      "transport": "streamable-http"
    }
  }
}