Skip to main content
Glama
Sign In
bearded-giant

spaceship-mcp

by bearded-giant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to spaceship-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Namecheap Server

      johnsorrentino
      A
      license
      B
      quality
      D
      maintenance
      Provides integration with the Namecheap API for domain management operations, including domain listing, availability checks, and nameserver configuration. It allows users to interact with their Namecheap account through natural language commands in MCP-compatible clients.
      3
      51 npm
      20
      MIT

    • spaceship-mcp

      heaventree
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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.
      108 npm
      MIT

    • namecheap-mcp

      fledgeling-co
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives an AI agent safe, high-level control over Namecheap domains – availability checks, registration, DNS, email forwarding, transfers, WhoisGuard privacy, and account balance via Namecheap's XML API. Designed for safe LLM interaction with built-in confirmation gates and read-modify-write DNS operations.
      20
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action boundaries, and the many DNS record creation tools are differentiated by record type. There is some overlap between save_dns_records and the type-specific create_*_record tools, but the descriptions explain when to use each.

    Naming Consistency4/5

    Names generally follow a predictable snake_case verb_noun pattern such as list_domains, get_domain, create_a_record, and delete_sellerhub_domain. A few names omit the resource or use slightly different phrasing, such as update_nameservers, but the convention remains readable and consistent overall.

    Tool Count2/5

    With 48 tools, the surface is very large for a single MCP server. Much of the count comes from separate DNS record-type creation tools, which could likely be consolidated or parameterized to reduce the tool burden.

    Completeness4/5

    The server covers most domain lifecycle, DNS, contact, nameserver, and SellerHub marketplace operations, including registration, renewal, transfer, restore, and async polling. Minor gaps exist, such as listing/deleting saved contacts or explicit domain deletion, but core workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources