dynadot-mcp
Related Servers
Alternatives to dynadot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP server for Dynadot domain registrar API3 — manage domains, DNS, contacts, transfers & more6736 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for managing domain registrations, DNS, WHOIS privacy, transfers, and marketplace listings via Spaceship API.3671 npm2MIT
- 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.1039 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the Spaceship API that enables AI-driven management of domains, DNS records, contacts, and marketplace listings.71 npm2MIT
- 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
Many tools have very similar purposes (e.g., eight set_default_* tools, multiple folder settings), but descriptions are detailed enough to distinguish them. However, with 105 tools, an agent may struggle to pick the right one quickly.
All tools use the dynadot_ prefix followed by a consistent verb_noun pattern in snake_case (e.g., dynadot_register, dynadot_set_dns). No mixing of conventions.
105 tools is far too many for a single server. This dramatically increases cognitive load and makes selection error-prone. The tool set should be split into multiple specialized servers.
The server covers an extensive range of domain management operations: registration, transfers, DNS, DNSSEC, contacts, folders, marketplace, auctions, and defaults. Minor gaps exist (e.g., no bulk update operation), but the surface is remarkably complete.