ens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THEGRAPH_API_KEY | Yes | Your API key from The Graph |
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_ens_nameA | Resolve an ENS name to its Ethereum address. |
| get_domain_detailsC | Fetch detailed information for an ENS domain, including its address. |
| get_domain_eventsC | Retrieve events associated with an ENS domain. |
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 3 tools
Each tool has a clearly distinct purpose: get_domain_details retrieves comprehensive domain information, get_domain_events focuses on event history, and resolve_ens_name performs a specific address resolution. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun naming pattern (get_domain_details, get_domain_events, resolve_ens_name), using snake_case throughout. The verbs 'get' and 'resolve' are appropriately descriptive and maintain a predictable structure.
With only 3 tools, the set feels somewhat thin for an ENS domain management server. While the tools cover key read operations, the scope could benefit from additional tools for broader ENS interactions, such as registration or ownership updates, to better support agent workflows.
The tools provide good read coverage for ENS domains (details, events, resolution), but there are notable gaps for write operations like registering, updating, or transferring domains. This limits the server's ability to handle full domain lifecycle management, though agents can work with the available read functions.