Schema | DomainScout

DomainScout

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`DOMAINSCOUT_DNS`	No	DNS pre-check (on/off)	on
`DOMAINSCOUT_TLDS`	No	TLDs tried for names given without one	com,net,ai
`DOMAINSCOUT_PRICES`	No	Public price lists (on/off)	on
`DOMAINSCOUT_AFFILIATE`	No	Affiliate buy links (on/off; off gives plain links)	on
`DOMAINSCOUT_REGISTRARS`	No	Registrars to show buy links for, e.g. cloudflare,porkbun,namecheap	all
`DOMAINSCOUT_TIMEOUT_MS`	No	Timeout of one request in milliseconds	10000
`DOMAINSCOUT_CONFIRM_MAX`	No	Free domains per call confirmed through your registrar API	50
`DOMAINSCOUT_DNS_SERVERS`	No	DNS servers to use, comma-separated	system
`DOMAINSCOUT_MAX_DOMAINS`	No	Domains per call, after adding TLDs	500
`DOMAINSCOUT_NAMECOM_TOKEN`	No	Name.com API token
`DOMAINSCOUT_MAX_CONCURRENCY`	No	Network requests in flight at once	10
`DOMAINSCOUT_PORKBUN_API_KEY`	No	Porkbun API key
`DOMAINSCOUT_NAMECOM_USERNAME`	No	Name.com username
`DOMAINSCOUT_SPACESHIP_API_KEY`	No	Spaceship API key
`DOMAINSCOUT_PORKBUN_SECRET_KEY`	No	Porkbun secret key
`DOMAINSCOUT_CLOUDFLARE_API_TOKEN`	No	Cloudflare API token with Registrar permission
`DOMAINSCOUT_PER_HOST_CONCURRENCY`	No	Requests in flight to one RDAP server	2
`DOMAINSCOUT_SPACESHIP_API_SECRET`	No	Spaceship API secret
`DOMAINSCOUT_CLOUDFLARE_ACCOUNT_ID`	No	Cloudflare account ID

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

Capability	Details
`tools`	{ "listChanged": true }
`resources`	{ "listChanged": true }

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
check_domainsA	Checks whether domain names are free to register. Built for bulk search: almost every good .com is taken, so brainstorm many candidates and pass them ALL in one call - hundreds of names are fine - instead of checking names one by one. Runs on the user's machine: DNS first, then the registry itself (RDAP, or WHOIS where there is no RDAP), in parallel within polite rate limits. Input: names with or without a TLD. "acme" is tried in every TLD from `tlds` (default: com, net, ai); "acme.io" is checked exactly as given. URLs work too. For a long list, pass only the TLDs the user wants (e.g. ["com"]): every name is checked in every TLD. Statuses: available: a registrar API confirmed it can be registered (only when the user set registrar API keys); `premium` says whether it costs more than the standard price. likely_available: not in the registry or DNS. Premium or registry-reserved names look the same, so the final price is on the registrar's page. taken: registered. May note that it is in deletion and may become available soon. reserved: blocked by the registry, or not sellable according to the registrar. unknown: could not verify right now (rate limit or timeout); try again later. Free domains come with buy links, cheapest first, with standard per-year prices where public price lists exist, or the exact price when a registrar confirmed the name. When many names are free, the text lists each on one line with its cheapest offer; check the user's favourites again to get every registrar's link. How to present the answer: list the free domains with their price and their buy link from this result - a table with a link column works well - so the user can register a name in one click. Keep the links; do not replace them with links of your own. Mention the renewal price when it differs from the first year, and any minimum term. Pass on the NOTES and, when present, the affiliate disclosure line. New names on request: when the user asks to regenerate, or for more or similar names, suggest only names that were not checked before, and pass the domains the user saved in `saved` so they stay in the results.

check_domainsA

Checks whether domain names are free to register. Built for bulk search: almost every good .com is taken, so brainstorm many candidates and pass them ALL in one call - hundreds of names are fine - instead of checking names one by one. Runs on the user's machine: DNS first, then the registry itself (RDAP, or WHOIS where there is no RDAP), in parallel within polite rate limits.

Input: names with or without a TLD. "acme" is tried in every TLD from tlds (default: com, net, ai); "acme.io" is checked exactly as given. URLs work too. For a long list, pass only the TLDs the user wants (e.g. ["com"]): every name is checked in every TLD.

Statuses:

available: a registrar API confirmed it can be registered (only when the user set registrar API keys); premium says whether it costs more than the standard price.
likely_available: not in the registry or DNS. Premium or registry-reserved names look the same, so the final price is on the registrar's page.
taken: registered. May note that it is in deletion and may become available soon.
reserved: blocked by the registry, or not sellable according to the registrar.
unknown: could not verify right now (rate limit or timeout); try again later.

Free domains come with buy links, cheapest first, with standard per-year prices where public price lists exist, or the exact price when a registrar confirmed the name. When many names are free, the text lists each on one line with its cheapest offer; check the user's favourites again to get every registrar's link.

How to present the answer: list the free domains with their price and their buy link from this result - a table with a link column works well - so the user can register a name in one click. Keep the links; do not replace them with links of your own. Mention the renewal price when it differs from the first year, and any minimum term. Pass on the NOTES and, when present, the affiliate disclosure line.

New names on request: when the user asks to regenerate, or for more or similar names, suggest only names that were not checked before, and pass the domains the user saved in saved so they stay in the results.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
`results-card`	Interactive panel for check_domains results: the free domains with prices and buy buttons.

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

Scored 2026-10-17 00:50 across 1 tool

Disambiguation5/5

With only one tool in the set, there is no other tool to confuse it with. The tool's purpose is singular and clearly defined, so an agent cannot misselect.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern in snake_case (check_domains). With no other tools, there are no deviations or inconsistent conventions to worry about.

Tool Count3/5

The server has only one tool, which the rubric considers borderline thin (1-2 tools). While the tool is comprehensive and handles the entire domain-checking workflow, the low count leaves some doubt about whether it is optimally scoped.

Completeness5/5

The tool covers all aspects of domain availability checking: DNS, RDAP, WHOIS, multiple TLDs, bulk input, statuses, buy links, and premium/price details. No obvious gaps exist for this domain.

Maintenance

ActivityMaintained

ResponsivenessNo issues