Skip to main content
Glama
danielgtmn

domain-mcp

by danielgtmn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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_domainB

Check if a single domain is available or registered.

Args:
    domain: Domain name to check (e.g. example.com, bücher.de).
    include_raw: Include raw RDAP/WHOIS payload (verbose).
    use_cache: Use in-memory TTL cache (default 5 minutes).

Returns:
    Status (available/registered/unknown/…), registrar, dates, nameservers.
check_domainsA

Check multiple domains in parallel (rate-limit friendly bulk check).

Args:
    domains: List of domain names (max recommended: 50 per call).
    include_raw: Include raw payloads (large responses).
    use_cache: Use in-memory TTL cache.

Returns:
    Summary counts plus a results list in the same order as input.
domain_infoA

Get registration details for a domain (registrar, expiry, nameservers).

Same underlying check as check_domain; prefer this when you need WHOIS-like
metadata for a domain you already know is registered.

Args:
    domain: Domain name to look up.
    include_raw: Include raw RDAP/WHOIS payload.
list_supported_tldsA

List TLDs with known RDAP endpoints (IANA bootstrap + overrides).

TLDs missing from this list may still work via WHOIS fallback.

clear_domain_cacheC

Clear the in-memory domain check cache.

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

A3.5/5.0

Scored across 5 tools

Disambiguation4/5

The tools are mostly distinct: check_domain and check_domains are clearly single vs bulk variants, while domain_info is differentiated by its stated purpose (metadata for known-registered domains). However, check_domain and domain_info perform essentially the same underlying check, which could cause mild misselection; the description mitigates this but the overlap is real.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (check_domain, check_domains, domain_info, list_supported_tlds, clear_domain_cache). Minor deviation: domain_info uses 'info' rather than a clearer verb like 'get_domain_info', breaking the otherwise clean pattern, and clear_domain_cache uses an adjective+noun rather than object-first.

Tool Count4/5

Five tools is within the ideal 3-15 range and appropriate for a domain-checking server. The count feels slightly trimmed—check_domain and domain_info are near-duplicates, suggesting one could be folded into the other—but the overall scope is reasonably well served.

Completeness4/5

The server covers checking, bulk checking, metadata lookup, TLD discovery, and cache management, covering the core domain-lookup workflows well. Minor gaps exist: there is no tool for WHOIS-style detailed records beyond raw payloads, and no capability to register or manage domains (if that were in scope). For pure lookups, the surface is complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources