Skip to main content
Glama

Related Servers

Alternatives to domeneshop-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Gandi domains and LiveDNS records directly via the Gandi API v5. It supports comprehensive domain management operations and full CRUD functionality for various DNS record types.
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check domain availability, purchase domains via Stripe, and perform full DNS and nameserver management. It facilitates automated domain lifecycle tasks like record updates and transfer locks without requiring CAPTCHAs.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables natural language domain management through Dynadot, supporting domain registration, DNS configuration, transfers, WHOIS contacts, and bulk operations across 106 API actions.
      10
      45 npm
      13
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to check domain availability, register and renew domains, and manage DNS records, contacts, and transfers through a registrar API.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to perform comprehensive domain management tasks through the Name.com API, including registration, DNS management, and transfers. It dynamically generates tools from the OpenAPI specification to facilitate natural language interaction with all Name.com services.
      55 npm
      3
      MIT

    TDQS

    A3.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Resources are cleanly partitioned (domains, DNS records, HTTP forwards, invoices) and the four DNS write tools (create/update/patch/upsert) are explicitly differentiated, including a cross-reference telling the agent to prefer patch_dns_record. The only residual risk is that update/upsert/patch all mutate a record and an agent could pick wrong, but the descriptions genuinely resolve this.

    Naming Consistency5/5

    Every tool follows the same snake_case verb_noun pattern (list_domains, get_dns_record, create_forward, patch_dns_record, update_dyndns). The verb set is small and applied predictably across all four sub-resources.

    Tool Count4/5

    17 tools across four sub-domains (2 domain, 7 DNS, 5 forward, 2 invoice) is proportionally balanced and each tool covers a distinct operation. It sits just outside the ideal 3-15 band and the four DNS mutation tools add some redundancy.

    Completeness4/5

    DNS records and HTTP forwards both have full CRUD plus partial-update and upsert, and domains/invoices are readable with useful filters. Gaps are minor and likely intentional: no domain settings/nameserver update or domain deletion, and invoices are read-only, but the core workflows are all reachable.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing