ens-mcp
Related Servers
Alternatives to ens-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceHosted, API-key-free MCP server that enables AI agents to interact with the Ens protocol via deterministic tool mappings to real endpoints.-
- AlicenseAqualityDmaintenanceMCP server for DNS lookups, reverse DNS, WHOIS, and domain checks. Zero auth, zero config.555 npm3MIT
- AlicenseAqualityDmaintenanceMCP server providing DNS resolution, reverse DNS, RDAP-based WHOIS, and IP geolocation lookups. No API keys required , and all upstreams are public.4MIT
- AlicenseAqualityCmaintenanceAn MCP server for domain name availability checking, WHOIS lookups, and domain suggestions — no API key required.436 npmMIT
- AlicenseAqualityCmaintenanceModel Context Protocol (MCP) server for deep DNS resolution, nameserver propagation, and DNSSEC validation1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for domainagent.dev, enabling AI agents to search, register, deploy, host, and manage domains with USDC payment on Base via x402. Supports static site deployment via Cloudflare Pages and DNS management.5 npmMIT
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.