spaceship-mcp
Related Servers
Alternatives to spaceship-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for the Spaceship API that enables AI-driven management of domains, DNS records, contacts, and marketplace listings.712MIT
- AlicenseBqualityDmaintenanceMCP server for managing domain registrations, DNS, WHOIS privacy, transfers, and marketplace listings via Spaceship API.36712MIT
- AlicenseNot gradedqualityNot gradedmaintenanceA lightweight MCP server for managing DNS records, purging cache, and interacting with the Cloudflare API through natural language commands.24-
- AlicenseNot gradedqualityCmaintenanceMCP server for reading and changing DNS records via the Spaceship API, with reviewable two-step confirmation and safety restrictions. It exposes only safe DNS operations, using domain allowlisting and failing closed when not configured.71MIT
- AlicenseBqualityAmaintenanceOfficial MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.1002591MIT
- AlicenseBqualityCmaintenanceMCP server for Openprovider.com that enables domain management actions such as checking availability, registering domains, listing domains, and managing contacts through natural language.10MIT
TDQS
Scored across 48 tools
Most tools have clearly distinct purposes, especially across different domains (domain management, DNS, contacts, seller hub). However, the many DNS record creation tools (e.g., create_a_record, create_cname_record) are very similar in behavior and warnings, which could cause some confusion despite clear record-type differentiation.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_domain_availability, set_auto_renew, create_cname_record). No mixing of conventions or vague verbs.
48 tools is a high count, but the server covers multiple subdomains (domain registration, DNS management, contacts, seller hub). While each tool has a clear role, the number feels borderline heavy for a typical MCP server, partly due to many per-record-type DNS tools.
The server provides comprehensive coverage for domain lifecycle (register, renew, restore, transfer, contacts, privacy, nameservers) and extensive DNS record management. Minor gaps like missing batch operations or advanced DNS features (e.g., dynamic DNS) are acceptable for the scope.