ENS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROVIDER_URL | No | Ethereum RPC provider URL(s). Multiple providers can be comma-separated. If not specified, default public nodes (like eth.drpc.org or eth.llamarpc.com) are used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve-nameB | Resolve an ENS name to an Ethereum address |
| reverse-lookupB | Get the ENS name for an Ethereum address |
| get-text-recordC | Get a text record for an ENS name |
| check-availabilityA | Check if an ENS name is available for registration |
| get-all-recordsB | Get all available information for an ENS name |
| get-subdomainsC | Get subdomains for an ENS name |
| get-name-historyC | Get the history of an ENS name |
| get-registration-priceC | Get the price to register an ENS name |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.