dynadot-mcp
Related Servers
Alternatives to dynadot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server for Dynadot domain registrar API3 — manage domains, DNS, contacts, transfers & more6766 npm2MIT
- AlicenseBqualityBmaintenanceMCP server for managing domain registrations, DNS, WHOIS privacy, transfers, and marketplace listings via Spaceship API.362MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for domain portfolio management, registrar operations, marketplace, and DNS management via CLI or AI agents.1,085 npm1Apache 2.0
- AlicenseAqualityDmaintenanceComprehensive MCP server for the Namecheap API, enabling domain management, DNS record control, nameserver settings, and domain registration from any MCP client.10MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the Spaceship API that enables AI-driven management of domains, DNS records, contacts, and marketplace listings.128 npm4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for domain management, enabling domain availability checks, bulk domain checks, and API connectivity testing through the RealtimeRegister API.11 npm1MIT
TDQS
Scored across 105 tools
Most tools map cleanly to a resource+action, but several clusters overlap: dynadot_search vs dynadot_bulk_search are explicitly aliases, dynadot_get_ns vs dynadot_server_list both enumerate nameservers, and dynadot_add_ns / dynadot_register_ns / dynadot_set_ns_ip are hard to tell apart. dynadot_set_folder (moves a domain) vs dynadot_set_folder_name (renames a folder) is also easy to misselect despite good descriptions.
The dynadot_ prefix is consistent, but the verb/noun ordering is not: some tools are verb_noun (get_dns, set_ns, list_coupons) while many are noun_verb (domain_list, folder_list, server_list, backorder_request_list), and a set of tools are bare verbs (renew, register, restore, search). It remains readable, but there is no single predictable pattern across 105 tools.
105 tools is far beyond a comfortable surface for an agent, and the same capability is fragmented across near-duplicates (search/bulk_search, get_ns/server_list). While the domain-registrar scope is genuinely broad, the count reflects one-tool-per-API-command rather than a well-curated set.
Coverage is deep: registration, transfer in/out, renewal, grace delete/restore, DNS, nameservers, DNSSEC, contacts, folders, privacy, auctions, backorders, and marketplace operations are all present. Notable gaps remain, such as an explicit unlock_domain alongside lock_domain and bulk domain-level operations outside the folder mechanism.