Name Whisper — ENS Intelligence Layer

Approve or revoke an operator for ENS contract interactions.

An approved operator can transfer ANY token owned by the approver on the specified contract. This is setApprovalForAll — it covers all tokens, not just one.

Contracts:

• base_registrar — ERC-721 tokens (unwrapped .eth names)

• name_wrapper — ERC-1155 tokens (wrapped names and subnames)

• ens_registry — ENS node ownership

Common use cases:

• Approve NameWrapper on BaseRegistrar before wrapping a name

• Approve a marketplace contract for trading

• Approve a management contract for batch operations

• Revoke a previously approved operator

Contract addresses:

• BaseRegistrar: 0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85

• NameWrapper: 0xD4416b13d2b3a9aBae7AcD5D6C2BbDBE25686401

• ENS Registry: 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e

WARNING: Only approve addresses you trust. An approved operator can move ALL your names on that contract.

Register multiple ENS names in bulk — batched into just 2 transactions (commit + register) via Multicall3.

Much cheaper and faster than registering names one at a time. Supports up to 20 names per batch.

Flow: batchCommit (1 tx) → wait 60 seconds → batchRegister (1 tx with total ETH). Excess ETH is refunded.

Each name gets its own secret for front-running protection. All names must be available for registration.

After registration, use bulk_set_records to configure all names at once with addresses, text records, and content hashes.

Set ENS resolver records for multiple names in a single transaction — bulk record editing.

All record updates across all names are batched into one resolver.multicall() call. Much cheaper than setting records one name at a time.

Supports the same record types as set_ens_records: address records (ETH, BTC, SOL, etc.), text records (avatar, description, social handles, AI agent metadata), content hash (IPFS/IPNS), and ENSIP-25 agent-registration records.

You can set different records for each name (e.g., unique avatars) or the same records across all names (e.g., same ETH address).

Max 50 names per batch. The wallet signing the transaction must be the owner/manager of all included names.

Transfer multiple ENS names in a single transaction via Multicall3 — bulk send.

Much cheaper and faster than transferring names one at a time. Supports up to 20 names per batch.

Automatically detects whether each name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and builds the correct transfer call for each.

All names can go to the same recipient or to different recipients — specify a toAddress per name.

Requirements:

• The fromAddress must currently own ALL names in the batch

• All addresses must be valid Ethereum addresses

• Names must be registered (not expired)

WARNING: This transfers FULL ownership of every name. Recipients gain complete control.

Resolver records (avatar, addresses, etc.) are NOT affected by transfer — they stay on each name.

After transfer, consider using bulk_set_records to update ETH address records on the transferred names.

Check availability of one or more ENS names. Returns status (AVAILABLE, REGISTERED, EXPIRED, or INVALID), owner address, and expiry date for each name. Validates ENS character rules. Accepts names with or without .eth suffix.

Extend the expiry of an ENS subname in the NameWrapper.

Subnames have their own expiry that cannot exceed the parent name's expiry. This tool extends a subname's expiry.

Who can call this:

• The parent name owner (always)

• The subname owner (only if CAN_EXTEND_EXPIRY fuse is burned on the subname)

Use cases:

• Extending subnames you've issued to users

• Self-extending your own subname (if CAN_EXTEND_EXPIRY is set)

• Keeping organizational subnames active

Scan the ENS marketplace for alpha — names listed below their comparable-sales valuation. Returns ranked opportunities with discount percentage, estimated value range, confidence rating, and comparable data. The autonomous agent's edge: find mispriced names before anyone else. Pair with get_valuation for deep analysis, then purchase_name to execute.

Check if an ENS name or wallet is a registered AI agent. Returns ENSIP-25 agent-registration verification (text record bindings between ENS names and on-chain agent registries), AI metadata from text records, and ERC-8004 reputation data when available.

ENSIP-25 verification is live: reads agent-registration text records from the name's resolver to confirm the ENS name ↔ registry binding.

ERC-8004 reputation queries (scores, reviews, validations) use the live mainnet contracts deployed January 29, 2026.

Returns the authenticated identity of the calling agent. If you connected with ERC-8128 signed requests, this resolves your wallet address to your ENS name, agent metadata, and portfolio summary. Call this first to confirm your identity is recognized.

Requires ERC-8128 authentication (signed HTTP requests). See GET /mcp/auth for setup details.

Get recent ENS marketplace activity — sales, new listings, offers, mints, transfers, renewals, and burns. Filter by event type. Returns event details including name, price (in ETH), buyer/seller addresses, and timestamp. Sorted by most recent first.

Get full details for a specific ENS name including owner, expiry, tags, active listings (with prices in ETH and USD), active offers, and ENSIP-25 agent identity bindings (if any agent-registration text records are set).

Check what primary ENS name is set for a wallet address (reverse resolution).

Returns the ENS name that this address resolves to, or null if no primary name is set.

This verifies both directions:

• Reverse: address → name (the reverse record)

• Forward: name → address (confirms the name actually points back to this wallet)

If either direction is missing, the primary name won't resolve. Use this to:

• Verify a primary name was set correctly after set_primary_name

• Check if a wallet has any primary name configured

• Debug why a primary name isn't showing up (missing ETH address record)

Find ENS names semantically similar to a given name using vector embeddings across 3.6M+ names. Returns similar names with similarity scores and live marketplace data (price, owner, expiry). Great for discovering related names for portfolio building or brand exploration.

Get usage statistics for this MCP server session. Returns tool call counts, success rates, and average latency.

Get a confidence-rated valuation for an ENS name based on comparable sales, entity recognition (Wikipedia/Wikidata), search interest, word frequency, and fame-scaled pricing. Returns estimated value range, background context on the name (person/place/brand/concept), comparable sales data, and a narrative explaining the valuation methodology. Essential for pricing decisions.

Get all ENS names owned by a wallet address. Returns each name with label, tags, expiry, registration date, and active listing/offer prices. Useful for portfolio analysis and wallet profiling.

If you are authenticated via ERC-8128 and omit the wallet parameter, your own wallet is used automatically.

Submit an offer (bid) on a registered ENS name. Validates the offer, provides market context (listing price, comparable sales, existing offers), and directs you to execute on the Vision marketplace.

Requires wallet signature for on-chain execution via Seaport protocol. The name owner can accept, counter, or decline on ensvision.com.

Tip: Use get_valuation first to understand fair market value before making an offer.

Get comprehensive management info for an ENS name.

Returns:

• Registration status (active, expiring soon, grace period, premium auction, expired, available)

• Exact expiry date and days remaining

• Whether the name is wrapped (NameWrapper) or unwrapped (BaseRegistrar)

• Current owner address

• Renewal pricing (on-chain)

• Recommended actions based on current status

Use this before performing any management action (renew, transfer, set records) to understand the current state of a name.

Manage fuses on a wrapped ENS name. Fuses are permission bits that can be permanently burned to restrict what can be done with a name.

Three modes:

1. read — Check which fuses are currently burned on a name

2. burn_owner_fuses — Burn fuses on a name you own (CANNOT_UNWRAP must be burned first)

3. burn_child_fuses — As a parent, burn fuses on a subname (e.g. burn PARENT_CANNOT_CONTROL on sub.parent.eth)

Owner-controlled fuses:

• CANNOT_UNWRAP — prevents unwrapping (MUST be burned first before any other fuse)

• CANNOT_BURN_FUSES — prevents burning additional fuses

• CANNOT_TRANSFER — prevents transfers

• CANNOT_SET_RESOLVER — prevents resolver changes

• CANNOT_SET_TTL — prevents TTL changes

• CANNOT_CREATE_SUBDOMAIN — prevents creating new subnames

• CANNOT_APPROVE — prevents approving operators

Parent-controlled fuses (for subnames):

• PARENT_CANNOT_CONTROL — parent permanently gives up control over the subname

• CAN_EXTEND_EXPIRY — allows the subname owner to extend their own expiry

WARNING: All fuse burning is IRREVERSIBLE. Fuses expire when the name expires.

Bulk create subnames under a parent ENS name. Designed for agent fleet deployment — create identities like agent001.company.eth, agent002.company.eth, etc. Each subname can have its own owner and records (addresses, text records). Uses the ENS NameWrapper for subname creation.

Returns complete transaction recipes (contract address, encoded calldata, gas estimates) for each subname. Your wallet signs and broadcasts the transactions. Subnames are free to create — only gas costs apply.

Provision a complete ENS identity for an AI agent in one call. Describe your agent's purpose and budget — get back recommended available names, registration recipes (contract, ABI, params), suggested ENS records (ai.agent, ai.capabilities), and ready-to-sign transaction data.

Supports ENSIP-25 agent-registration binding for cryptographically verifiable agent identity. After registration, use set_ens_records to apply the suggested records.

Example: "DeFi trading bot, 0.05 ETH budget" → names like swiftswap.eth with full registration instructions.

Purchase an ENS name — either buy a listed name from a marketplace or register an available name directly on-chain.

For AVAILABLE names: Returns a complete registration recipe with contract address, ABI, step-by-step instructions, and a pre-generated secret. Your wallet signs and submits the transactions (commit → wait 60s → register).

For LISTED names: Searches all marketplaces (OpenSea, Grails) for the best price. If there are MULTIPLE active listings, returns CHOOSE_LISTING status with all options — present these to the user and ask which one they want. When the user chooses, call this tool again with the chosen orderHash to get the buy transaction.

The tool auto-detects whether the name is available or listed. You can override with the 'action' parameter.

Reclaim ENS Registry ownership of a .eth name.

This syncs the ENS Registry owner to match the BaseRegistrar token owner. Used when:

• A name was transferred via direct safeTransferFrom (bypassed ENS routing)

• ENS Registry ownership is out of sync with token ownership

• Recovery after a contract migration or edge case

The caller must own the BaseRegistrar ERC-721 token for the name. After reclaiming, you may also need to set the resolver if it was cleared.

Renew an ENS name or batch of names. Returns the transaction data needed to extend registration.

Unlike registration, renewal is simple — just one transaction with payment. No commit/reveal needed.

Accepts ANY duration — days, weeks, months, years. There is no minimum renewal period on ENS. Examples: 7 days (1 week), 28 days (1 month), 365 days (1 year).

Anyone can renew any name (you don't need to be the owner). This is useful for:

• Extending your own names before expiry

• Gifting renewal to a friend's name

• Protecting valuable names from expiring

Returns exact on-chain pricing from the ETHRegistrarController with a 5% buffer (excess is refunded).

For batch renewals (multiple names), all names are bundled into a SINGLE Multicall3 transaction.

Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains).

Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles.

Examples:

• "trading agents on Base" → search for trading agents filtered to Base chain

• "MCP agents" → find agents that support the Model Context Protocol

• "high reputation agents" → set minReputation to find top-scored agents

Search ENS names using natural language. Supports all query types:

• Filtered search: "4-letter words under 0.1 ETH"

• Concept search: "ocean themed names" (semantic similarity across 3.6M names)

• Creative search: "names for a coffee brand" (AI-generated suggestions)

• Collection search: "crypto terms expiring soon"

• Activity: "what sold recently?"

• Availability check: "is coffee.eth taken?"

• Bulk check: "check apple.eth, banana.eth, cherry.eth" Returns structured results with name, price, owner, tags, and availability info.

Search the ENS knowledge base — governance proposals, protocol documentation, developer insights, blog posts, forum discussions, and Farcaster casts from key ENS figures (Vitalik, Nick Johnson, etc.). Covers ENS governance and DAO proposals, protocol details (ENSv2, resolvers, subnames), community sentiment, historical decisions, and what specific people have said about a topic. Powered by semantic search over curated ENS sources.

Do NOT use this for name valuations, market data, or availability checks — use the other tools for those.

Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast.

Supports address records (ETH, BTC, SOL, etc.), text records (avatar, description, url, social handles, AI agent metadata), content hash (IPFS/IPNS), and ENSIP-25 agent-registration records.

Multiple records are batched into a single multicall transaction to save gas.

Common text record keys: avatar, description, url, email, com.twitter, com.github, com.discord, ai.agent, ai.purpose, ai.capabilities, ai.category.

ENSIP-25 support: Pass agentRegistration with registryAddress and agentId to automatically set the standardized agent-registration text record. This creates a verifiable on-chain binding between your ENS name and your agent identity in an ERC-8004 registry.

The returned transaction can be signed and submitted directly using any wallet framework (Coinbase AgentKit, ethers.js, etc.).

Set the primary ENS name (reverse resolution) for a wallet address.

This controls what name is displayed when someone looks up your Ethereum address. For example, instead of seeing "0x1234...abcd", they'd see "myname.eth".

Requirements:

• You must own or control the ENS name

• The name's ETH address record must point to your wallet

• Only the wallet owner can set their own primary name

If the ETH address record doesn't match, use set_ens_records first to update it.

Only one primary name per address — setting a new one replaces the previous.

Change the resolver contract for an ENS name.

The resolver is where a name's records live (ETH address, text records, content hash, etc.). Changing the resolver points the name at a different contract.

Common use cases:

• Migrating to the latest ENS Public Resolver

• Pointing to a custom resolver (e.g. for off-chain/CCIP-read resolution)

• Fixing a name that has no resolver set

Pass "public" as the resolver address to use the ENS Public Resolver (0x231b0Ee14048e9dCcD1d247744d114a4EB5E8E63).

WARNING: Records on the old resolver won't be visible after switching. Set up records on the new resolver first, or use the ENS Public Resolver which most names already use.

Transfer ownership of an ENS name to another wallet address.

Automatically detects whether the name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and builds the correct transaction.

Requirements:

• The fromAddress must currently own the name

• Both addresses must be valid Ethereum addresses

• The name must be registered (not expired)

WARNING: This transfers FULL ownership. The recipient gains complete control including the ability to transfer, set records, or let the name expire.

Resolver records (avatar, addresses, etc.) are NOT affected by transfer — they stay on the name.

Unwrap a .eth name from the ENS NameWrapper back to BaseRegistrar.

This converts the name from an ERC-1155 token back to an ERC-721 token. All fuses are cleared upon unwrapping.

Will fail if the CANNOT_UNWRAP fuse has been burned — that restriction is permanent.

Use cases:

• Reverting a wrapped name to standard ERC-721 for compatibility

• Regaining full control after wrapping without burning CANNOT_UNWRAP

• Moving a name to a platform that only supports ERC-721

Check if an ENS sale is a wash trade. Provide either a tx_hash to look up a pre-computed score, or provide label + buyer + seller + price_eth for live on-demand analysis. Returns a wash confidence score (0-1), a label (clean/suspicious/likely_wash), detected signals, and a human-readable summary.

Wrap an unwrapped .eth name into the ENS NameWrapper contract.

Wrapping converts the name from an ERC-721 token (BaseRegistrar) to an ERC-1155 token (NameWrapper). This enables:

• Fuse permissions (restrict what can be done with the name)

• Protected subnames (subnames with guaranteed permissions)

• ERC-1155 compatibility for marketplaces and protocols

Returns a two-step transaction recipe: approve + wrap.

Available fuses (all IRREVERSIBLE once burned):

• CANNOT_UNWRAP — prevents unwrapping back to BaseRegistrar

• CANNOT_BURN_FUSES — prevents burning additional fuses

• CANNOT_TRANSFER — prevents transfers

• CANNOT_SET_RESOLVER — prevents resolver changes

• CANNOT_SET_TTL — prevents TTL changes

• CANNOT_CREATE_SUBDOMAIN — prevents new subnames

• CANNOT_APPROVE — prevents approving operators

CANNOT_UNWRAP must be burned before any other fuses can be burned.