ENS MCP Server
This ENS MCP Server enables interaction with the Ethereum Name Service (ENS) to query, resolve, and manage blockchain domain names:
Resolve ENS names - Convert human-readable names (like 'vitalik.eth') to Ethereum addresses
Reverse lookup addresses - Find the ENS name associated with a given Ethereum address
Retrieve text records - Access metadata including email, URL, avatar, description, and social media handles
Check name availability - Determine if an ENS name is available for registration and get owner information if already registered
Get comprehensive name information - Fetch all available data including resolver address, text records, linked addresses, content hash, ownership, and expiration details
List subdomains - Discover all subdomains associated with an ENS name along with their owner information
View name history - Access historical events such as transfers, resolver changes, and registration events
Calculate registration costs - Get price breakdowns for registering ENS names with customizable duration, including base price, premium, and total
Enables Claude to interact with the Ethereum Name Service (ENS) system to resolve ENS names to Ethereum addresses, perform reverse lookups, retrieve records, check name availability, and access other ENS-related information
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ENS MCP Server resolve vitalik.eth to get his Ethereum address"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ENS MCP Server
MCP Server for Ethereum Name Service (ENS), enabling Claude to interact with the ENS system to resolve names, check availability, retrieve records, and more.
npm package: https://www.npmjs.com/package/mcp-server-ens
Tools
resolve-name
Resolve an ENS name to an Ethereum address
Required inputs:
name(string): The ENS name to resolve (e.g., 'vitalik.eth')
Returns: The corresponding Ethereum address or an error message
reverse-lookup
Get the ENS name for an Ethereum address
Required inputs:
address(string): The Ethereum address to look up
Returns: The corresponding ENS name or an indication that no name was found
get-text-record
Get a text record for an ENS name
Required inputs:
name(string): The ENS name to querykey(string): The record key to look up (e.g., 'email', 'url', 'avatar', 'description', 'twitter', etc.)
Returns: The value of the specified text record or indication that no record was found
check-availability
Check if an ENS name is available for registration
Required inputs:
name(string): The ENS name to check
Returns: Availability status and owner information if registered
get-all-records
Get all available information for an ENS name
Required inputs:
name(string): The ENS name to query
Returns: Comprehensive information including resolver address, text records, addresses, content hash, ownership, and expiration details
get-subdomains
Get subdomains for an ENS name
Required inputs:
name(string): The ENS name to query for subdomains
Returns: List of subdomains with their owner information
get-name-history
Get the history of an ENS name
Required inputs:
name(string): The ENS name to check history for
Returns: Historical events related to the name, including transfers, resolver changes, and registration events
get-registration-price
Get the price to register an ENS name
Required inputs:
name(string): The ENS name to check price for
Optional inputs:
duration(number, default: 1): Registration duration in years
Returns: Registration price breakdown including base price, premium, and total
Related MCP server: MCP Crypto Wallet EVM
Setup
Prerequisites
Node.js (v16 or higher)
npm or yarn
Access to Ethereum RPC providers (public or private)
Installation
Clone the repository or create a new project:
git clone https://github.com/JustaName-id/ens-mcp-serverInstall dependencies:
npm iConfigure Ethereum providers: Create a
.envfile in the project root with the following (optional):
PROVIDER_URL=https://your-provider-url.com,https://your-backup-provider.comIf no providers are specified, the server will use these defaults:
Usage with Claude Desktop
Add the following to your claude_desktop_config.json:
Using npx
{
"mcpServers": {
"ens": {
"command": "npx",
"args": [
"-y",
"mcp-server-ens"
],
"env": {
"PROVIDER_URL": "https://your-provider-url.com,https://your-backup-provider.com"
}
}
}
}Using local script
{
"mcpServers": {
"ens": {
"command": "node",
"args": [
"/path/to/your/server.js"
],
"env": {
"PROVIDER_URL": "https://your-provider-url.com,https://your-backup-provider.com"
}
}
}
}Usage with Claude Code
claude mcp add ens -- npx -y mcp-server-ensWith custom providers:
claude mcp add ens -e PROVIDER_URL="https://your-provider-url.com" -- npx -y mcp-server-ensVerify it's connected:
claude mcp listError Handling
The server implements robust error handling for various scenarios:
Network errors connecting to Ethereum providers
Invalid ENS names or Ethereum addresses
ENS-specific errors
General operational errors
All errors are normalized into user-friendly messages while preserving technical details for debugging.
Publishing
To publish as an npm package:
npm publish --access publicTroubleshooting
If you encounter errors:
Verify your Ethereum providers are working and accessible
Check that the ENS names you're querying are formatted correctly
Ensure you have the latest version of the ENS libraries
Try using multiple providers by comma-separating them in the PROVIDER_URL environment variable
License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Available Tools
8 toolscheck-availabilityA
Check if an ENS name is available for registration
Inputs: name (required).
get-all-recordsB
Get all available information for an ENS name
Inputs: name (required).
get-name-historyC
Get the history of an ENS name
Inputs: name (required).
get-registration-priceC
Get the price to register an ENS name
Inputs: name (required), duration.
get-subdomainsC
Get subdomains for an ENS name
Inputs: name (required).
get-text-recordC
Get a text record for an ENS name
Inputs: key (required), name (required).
resolve-nameB
Resolve an ENS name to an Ethereum address
Inputs: name (required).
reverse-lookupB
Get the ENS name for an Ethereum address
Inputs: address (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: availability checks, retrieving records/history/price/subdomains/text, resolving names, and reverse lookups. The descriptions make it easy to differentiate between tools like 'get-all-records' (comprehensive info) and 'get-text-record' (specific record type).
The naming follows a consistent verb-object pattern with hyphens (e.g., 'check-availability', 'get-all-records'), except for 'reverse-lookup' which uses a different verb style. This minor deviation slightly reduces consistency, but the overall pattern remains highly readable and predictable.
With 8 tools, the count is well-scoped for an ENS server, covering key operations like checking availability, retrieving various data types, resolving addresses, and reverse lookups. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset provides strong coverage for querying and resolving ENS names, including availability, records, history, price, subdomains, text records, and bidirectional resolution. A minor gap is the lack of write operations (e.g., registering or updating names), but the read-focused surface is nearly complete for its apparent purpose.
Maintenance
Related MCP Connectors
ENS names: resolve, read profiles and ownership, list names, prepare registrations and changes
44 MCP tools to search, value, register, trade, and manage ENS names. AI-powered intelligence layer.
EVM chain reads for agents: balances, gas, fees, blocks, txs, logs, ENS. 15 tools, x402 per call.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables Claude to interact with Ethereum nodes, allowing users to check ENS token balances, view smart contract code, and decode transactions through natural language.51MIT
- AlicenseBqualityDmaintenanceProvides Claude with access to Ethereum and EVM-compatible blockchain operations, enabling wallet management, transaction handling, contract interactions, and blockchain queries through natural language.35136 npm10MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with the Ethereum Name Service via natural language, supporting lookups, availability checks, pricing, subnames, and onchain records.15Apache 2.0
- AlicenseAqualityDmaintenanceAI-powered ENS intelligence for autonomous agents, enabling search, valuation, trading, and management of ENS domains via the Model Context Protocol.44AGPL 3.0