domain-checker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Local HTTP dev server only. | 3000 |
| LOG_LEVEL | No | debug | info | warn | error | silent | info |
| RAPIDAPI_KEY | Yes | Your RapidAPI key. Never commit it. | |
| RAPIDAPI_HOST | No | Rarely changed. | domainstatus.p.rapidapi.com |
| RATE_LIMIT_MAX | No | Tool calls per client per window. `0` disables. | 15 |
| RAPIDAPI_TIMEOUT_MS | No | Upstream request timeout (clamped 1000-60000). | 10000 |
| RATE_LIMIT_WINDOW_MS | No | Rate-limit window length. | 60000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domain_availabilityA | Check whether a domain name is available for registration. Provide the name and TLD separately (e.g. name "mybrand", tld "ai"). Returns availability, whether the TLD is valid, and which lookup method (usually WHOIS) was used. |
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 1 tool
There is only one tool, so an agent cannot confuse it with any other operation. The name and description clearly explain what it does and what inputs it expects.
The single tool uses a clear verb_noun convention: check_domain_availability. With only one tool, there are no naming clashes or inconsistent patterns to create confusion.
One tool is slightly under the typical 3-15 range, but for the server's narrow purpose of checking domain availability, it is a reasonable and focused surface. It could arguably include additional domain-related tools, but the count is not excessive or trivially mismatched.
For the stated purpose of checking whether a domain is available for registration, the tool covers the core operation fully: it validates the TLD, returns availability, and indicates the lookup method. There are no obvious dead ends within this narrow domain.