Skip to main content
Glama
imprvhub

Domain Availability Checker MCP

by imprvhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_TRANSPORTNoThe transport mode for the MCP server. Use 'stdio' for Claude Desktop integration (default) or 'sse' for HTTP/web deployments like Google Cloud Run.stdio

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_domainA

Check whether a specific domain name is registered.

Give a full domain such as "example.com". Availability comes from the registry's
RDAP service where one exists, which is authoritative; for TLDs without RDAP the
registry's WHOIS server and DNS are used, and the result may come back
"undetermined" rather than guessing.

Args:
    domain: The domain to check, e.g. "mysite.com". A bare name with no
        top-level domain is checked across the popular TLDs instead.
suggest_domainsA

Check one name across many top-level domains and report which are free.

Args:
    name: The second-level name to check, without a dot, e.g. "mysite".
    category: Which TLD set to check - "popular" (12 TLDs, the default),
        "country" (36), "new" (49) or "all" (roughly 95). Larger sets take
        proportionally longer.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.9/5.0

Scored across 2 tools

Disambiguation4/5

check_domain checks a single fully-qualified domain while suggest_domains sweeps one second-level name across many TLDs, so their core purposes differ. However, check_domain's fallback of checking a bare name across the popular TLDs partially duplicates suggest_domains' default 'popular' category, which could cause occasional misselection.

Naming Consistency5/5

Both tools follow a clean verb_noun pattern (check_domain, suggest_domains) with snake_case throughout. The parameter names (domain, name, category) are also consistent and descriptive.

Tool Count3/5

Two tools is thin even for a narrow availability-checking server; there is no single-vs-batch parity beyond TLD sweeps. It is defensible but borderline sparse.

Completeness4/5

The check-and-sweep pair covers the core lifecycle of domain availability lookup, including authoritative RDAP/WHOIS/DNS sources and TLD batching. Minor gaps remain: no way to check multiple distinct second-level names in one call and no results for pricing or registrar handoff.

Maintenance

ActivityMaintained
ResponsivenessSlow

Resources