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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
check_domainA
Check domain availability. 

Usage examples:
- "mysite.com --domain" - checks exact domain
- "mysite --domain" - checks mysite across all popular TLDs
- "test.io --domain" - checks test.io exactly, plus test across all TLDs

Args:
    domain_query (str): Domain to check with --domain flag
    
Returns:
    Dict containing availability results for the domain and suggested alternatives

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'check_domain' has a clear, distinct purpose that cannot be mistaken for any other functionality.

Naming Consistency5/5

The naming is perfectly consistent as there is only one tool following a clear verb_noun pattern ('check_domain'). No mixed conventions or deviations exist to evaluate.

Tool Count2/5

A single tool is too few for a server that appears to handle domain availability checking, as this domain typically involves related operations like bulk checks, WHOIS lookups, or domain suggestion generation. The tool count feels thin and incomplete for the apparent scope.

Completeness2/5

The tool surface is severely incomplete for domain availability checking. While 'check_domain' covers basic availability queries, there are significant gaps such as no tools for WHOIS information, bulk domain checks, domain suggestion algorithms, or TLD-specific searches, which are common in this domain and will limit agent effectiveness.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources