domain-checker
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| domain-checker_check_domain_toolB | Checks if a domain is available for registration by querying DNS records and RDAP data. |
| domain-checker_check_tlds_toolC | Checks a keyword across multiple top-level domains (TLDs) to find available domain names. |
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 specific domain's availability, and the other checks a keyword across multiple TLDs. No overlap.
Both tools follow a consistent verb_noun pattern with the 'check_' prefix and a common '_tool' suffix, making the naming predictable.
With only 2 tools, the set feels thin for a domain checker, but it covers the core use cases of checking a single domain and exploring multiple TLDs.
The tools cover basic domain availability checking and keyword search across TLDs, but lack additional operations like detailed WHOIS lookups or bulk checks, leaving notable gaps.