Skip to main content
Glama
yenyifu

MCP Domain Availability Server

by yenyifu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP Domain Availability Server

No user-submitted related servers found.

    Related Servers

    • Domain Checker MCP Server

      3viky
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check domain availability, perform batch domain lookups, and generate intelligent domain name suggestions across multiple TLDs using WHOIS integration.
      3
      MIT

    • nameinsight

      himan-patel
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to generate brandable business names and verify each candidate across TLDs with real registry lookups, ranking results by availability. Also checks individual or bulk domains for registration status, expiry, DNS, email and TLS details via RDAP, WHOIS and DNS probes.
      4
      MIT

    • mcp-server-canyougrab

      einiba
      A
      license
      A
      quality
      B
      maintenance
      Confidence-scored domain availability checking for AI agents via real-time DNS and WHOIS lookups. Bulk check up to 100 domains, WHOIS enrichment, and quota monitoring. All tools are read-only.
      3
      1
      MIT

    • DomainScout

      JohnDaka
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to bulk-check hundreds of brainstormed domain names in a single call, reporting which are available, taken, or reserved along with buy links and prices from multiple registrars. It runs locally via DNS, RDAP, and WHOIS lookups, with optional registrar API keys for confirming availability and premium pricing.
      4
      1
      491 npm
      3
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have clearly distinct purposes: one checks a single domain, while the other handles multiple domains. The descriptions reinforce this distinction, making misselection unlikely. However, the similarity in core functionality could cause minor confusion if an agent needs to decide between them for a single domain.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'check_' prefix and snake_case naming. The naming is predictable and readable, with no deviations in style or convention across the tool set.

    Tool Count3/5

    With only 2 tools, the server feels thin for a domain availability service. While the tools cover basic availability checks, the scope is limited, and more operations (e.g., domain suggestion, registration status, or pricing) might be expected. This borderline count could hinder agent workflows.

    Completeness2/5

    The tool set is significantly incomplete for a domain availability server. It lacks essential operations such as domain suggestion, registration initiation, pricing lookup, or WHOIS details retrieval. Agents will face dead ends when trying to perform common domain-related tasks beyond basic availability checks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources