Building the most comprehensive ENS management platform — and preparing for what is next.
AI agent integration: the MCP server
ENS.Tools is now AI-native. We have built a full Model Context Protocol (MCP) server that lets AI agents — Claude, ChatGPT, custom bots — query ENS data directly through our platform. No API keys, no rate limits, completely open.
The MCP endpoint exposes nine tools:
lookup_domain— full domain details (owner, expiry, resolver, records)check_expiry— batch expiry checking for multiple namessearch_domains— pattern-based searchget_owner_domains— list all domains owned by an addresscheck_agent_verification— verify ENSIP-25 AI agent registrationsis_name_available— availability with grace-period awarenessget_name_price— real-time pricing from ENS contractsget_subnames_for_name— list all subdomains for a parentget_name_history— full event history
The endpoint is live at ens.tools/mcp and the discovery manifest sits at ens.tools/.well-known/mcp.json. We have also published a comprehensive llms.txt describing everything ENS.Tools can do.
ENSIP-25: AI agent identity verification
As AI agents become first-class participants on Ethereum, verifying their identity matters. We now fully support ENSIP-25, the standard for registering AI agents to ENS names.
Domain owners can set agent-registration text records on their ENS name to cryptographically link AI agents to their identity — configurable directly from the Records Editor, no manual ABI encoding. When viewing any domain that has ENSIP-25 registrations, you will see a verification card showing the registered agents, their registry addresses, and agent IDs.
Profile completeness score
Ever wondered how complete your ENS profile is? Now there is a score for it. When viewing your own domain, you will see a circular completeness indicator that checks for avatar, description, website, email, social handles, ETH address, multi-chain addresses, content hash, and primary name. Each item is weighted by importance, and a "Complete your profile" button takes you straight to the editor.
Multi-chain addresses (ERC-7828)
ENS isn't just for Ethereum any more. We now display multi-chain addresses using the ERC-7828 name@chain format — the emerging standard for cross-chain resolution. vitalik.eth@optimism, vitalik.eth@base, and the full chain registry from the on.eth convention all surface on the domain detail page.
Direct ENS contract renewals
Renewals now go through the official ENS contracts — no intermediary, no wrapper, no custody. Single renewals use the ETH Registrar Controller; bulk renewals use the official Bulk Renewal contract; the 5% platform fee is transparently routed to enstools.eth. Every transaction you sign hits the ENS protocol directly on mainnet.
What we have built for ENS v2
- L1 on-chain data storage indicators on every domain page
- Wrapper status tracking — fuses, expiry, full visibility
- ERC-7828 multi-chain address rendering (already live)
- ENSIP-25 agent verification (already live)
- MCP server for AI-first interactions (already live)
Try it now
Everything in this post is live at ens.tools. Connect your wallet for your dashboard, explore the Expiry Explorer, or look up any domain on the redesigned detail pages.