5 things you can build with the ENS.Tools MCP server in 30 minutes

The ENS.Tools MCP server has been live for a few months and the inbound traffic from chatgpt.com is meaningful and growing. What that means in practice: AI agents are using it to answer ENS questions and execute lookups. If you're building agents, this is a free primitive — no API key for the public baseline; point your client at our endpoint and the current ENS and agent tool catalogue is available.

Here are five concrete things worth building.

Quick setup recap

The endpoint is:

https://ens.tools/mcp

Discovery manifest at https://ens.tools/.well-known/mcp.json. The live catalogue covers domain and record resolution, expiry, ownership, semantic discovery, market intelligence, ENSIP-25/26 and ERC-8004, transaction simulation, status tracking, and unsigned plans for common ENS and marketplace actions. All use Streamable HTTP.

Add it to Claude Desktop, Cursor, or any MCP-compatible client by pointing at the URL above. Smithery, Glama, and pulsemcp.com all list it.

1. "Expiry watchlist" agent

A scheduled agent that checks a list of ENS names you care about every day and pings you if any are entering grace period or temp premium.

Prompt shape:

For each of these names, use ens-tools/check_expiry to get the
current state and time remaining. List the ones with less than
30 days left. Output as a table.

Names: cool.eth, vault.eth, signal.eth, atlas.eth, ...

Pair with cron and you have a personal alert system without building any infrastructure. Total code: 10 lines if you're using a framework like Mastra or LangGraph.

2. "Should I buy this name?" valuation assistant

An agent that pulls multiple signals about a candidate name and synthesises a buy/skip recommendation: current price, historical sales, NameGuard security score, character pattern, expiry runway, comparable sales of similar names.

Tools used: lookup_domain, get_name_history,estimate_domain_value, get_name_price,marketplace_search.

Prompt shape:

I'm considering buying alex.eth for 5 ETH. Use ens-tools to:
- Get its full history and current state
- Look up comparable 4-letter dictionary names that sold recently
- Estimate its fair value
- Flag any security concerns

Then tell me: buy, negotiate, or skip — and why.

3. Marketplace floor sweep agent

Surface the cheapest names matching a pattern across all venues. The MCP's marketplace_search tool returns aggregated listings; pair with marketplace_stats for floor-price context.

Use case: "Find me the 10 cheapest 4-letter dictionary words listed under 0.05 ETH right now." Returns in seconds. Useful for thrift-shop collectors and for finding mispriced inventory.

4. Agent identity lookup (ENSIP-25)

ENSIP-25 lets you advertise an AI agent against your ENS name by writing an agent-registration text record naming a registry and an agent ID. The MCP exposes check_agent_verification to read those records back.

The verifier now checks both directions: the ENS record's registry and agent ID, and the ERC-8004 registration file's reference back to the ENS name. Results distinguish bidirectional verification, a registered but custodial or incomplete claim, a self-asserted claim, a mismatch, and no claim. That makes the evidence visible without pretending it is stronger than it is.

Look up the agent records an ENS name advertises:
- Name: agent.namehash.eth
- Claimed agent ID: 0xABC...

Use ens-tools/check_agent_verification and report the returned
verification grade and evidence, not just a boolean.

5. Agent launch and transaction planner

The write-planning tools prepare calldata, targets, values, dependencies, and human-readable checks without holding a private key or broadcasting. Agents can plan registration, renewal, records, transfers, subnames, ERC-8004 identity, Seaport listings, offers, and purchases.

Launch researcher.ses.eth as an agent.

1. Use ens-tools/provision_agent_identity to build the phases
2. Simulate every transaction with ens-tools/simulate_transaction
3. Show the user the exact effects and request wallet confirmation
4. Submit in dependency order and track each receipt

The signing boundary stays explicit: ENS.Tools prepares and checks; the user's wallet decides and signs.

Why MCP is the right primitive for this

Three reasons our MCP-first approach has worked better than the "publish a REST API" alternative we considered:

1. No API key for the public baseline. Reads and unsigned plans work with zero ceremony. Optional protected tiers can be advertised through standard OAuth metadata when configured.
2. Tool descriptions are part of the contract. The MCP spec includes tool definitions with parameter descriptions and purpose strings. AI clients read those and figure out which tool to use without us writing a separate docs site for the LLM audience.
3. Discovery via .well-known/mcp.json. Any MCP-aware client can find our server, learn what it offers, and register the tools — without us pushing or you configuring.

What is available now

The agent platform now includes:

• Unsigned transaction plans for registration, renewal, records, transfers, subnames, agent fleets, ERC-8004, and Seaport.
• ENSIP-26 context and MCP/A2A/Web endpoint discovery, plus a browsable agent directory and identity profiles.
• Aggregate-only usage analytics and dormant OAuth/payment capability flags that can be enabled without changing the public interface.

If you build something with the MCP, we want to hear about it. The best agents using ENS data are often ones we never would have thought of.

Discovery manifest: /.well-known/mcp.json →