MCP Domain Availability Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domain_availabilityA | Check if a domain name is available for registration. Uses DNS, RDAP, and WHOIS lookups. Returns availability status and details. |
| check_multiple_domainsB | Check availability for multiple domains at once (up to 50 domains). Returns results for all domains with summary statistics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.