Name Whisper — ENS Intelligence Layer

What Name Whisper — ENS Intelligence Layer does

Name Whisper — ENS Intelligence Layer MCP server gives MCP-compatible AI clients access to ENS discovery, market data, transactions, and name administration. Its discovery tools support natural-language search, entity enumeration, availability checks, similar-name lookup, detailed name metadata, and lifecycle searches for premium, grace-period, or soon-to-expire names.

The intelligence tools combine marketplace and on-chain data. They can estimate value using comparable sales, quality references, and a name's own sales history; inspect recent market activity; review a wallet's portfolio; identify listings priced below comparable-sales estimates; and flag possible wash trading. Entity recognition can use Wikipedia and Wikidata references.

Commerce operations include registration, purchases, offers, listings, renewals, and batch transactions. Management tools handle ownership transfers, resolver records, reverse resolution, resolver changes, NameWrapper operations, subnames, approvals, recovery, and ENS agent identity workflows. Several operations return transaction recipes or unsigned orders for a client or wallet to sign.

How it works

The npm package is a thin proxy rather than the data or transaction backend. When started locally, it registers the tool schemas with the MCP client, accepts MCP calls, and forwards them to namewhisper.ai/mcp over HTTPS. Backend services provide the indexed name data, valuation logic, marketplace aggregation, and on-chain transaction construction.

The package supports standard stdio use with npx -y namewhisper-mcp. A remote-capable MCP client can instead connect to https://namewhisper.ai/mcp, which serves the same tool set over streamable HTTP. No API key, local database, or application secret is required according to the supplied documentation.

Setup and configuration

For Claude Desktop or Cursor, add a server entry that runs npx with the -y namewhisper-mcp argument. Claude Code can register the same command with claude mcp add namewhisper -- npx -y namewhisper-mcp. Direct execution uses npx namewhisper-mcp.

Name Whisper — ENS Intelligence Layer can target a different backend through the NAMEWHISPER_URL environment variable. Its documented default is https://namewhisper.ai. Most installations therefore need no configuration beyond Node.js and an MCP client. Remote use does not require installing the package; configure the client with the HTTPS endpoint instead.

Tools and capabilities

The documented tool groups cover:

• Discovery: search, entity lists, metadata, availability, similar names, and expiring names.
• Intelligence: valuations, market events, wallet portfolios, discounted listings, wash-trading checks, and primary-name resolution.
• Commerce: single and batch purchases, sweeps, listings, offers, cancellations, registration, renewals, and bulk record updates.
• Management: transfers, records, primary names, resolver changes, wrapping, unwrapping, fuses, subnames, approvals, and ownership recovery.
• Agent identity and knowledge: ENSIP-25 and ERC-8004-related workflows, agent directory and reputation searches, ENS knowledge search, caller identity, and usage statistics.

Batch limits vary by operation: purchases, registrations, and transfers support up to 20 names, bulk listings support up to 10, and bulk record updates support up to 50. Seaport, Multicall3, and SIP-6 are used by the documented transaction flows where applicable.

Limitations and notes

Name Whisper — ENS Intelligence Layer depends on its hosted backend for valuation, indexed data, marketplace information, and transaction building. The local package does not provide an independent database or valuation engine. Actions that change ownership, listings, offers, records, or other on-chain state produce transactions or signing flows; the supplied material does not state that the server signs or submits them automatically.

Some operations are irreversible or financially consequential. In particular, fuse burning is described as irreversible, while purchases, offers, transfers, renewals, and record changes require appropriate wallet authorization and transaction review. The remote endpoint is intended for clients that support streamable HTTP, while local installation uses MCP stdio.