Domainnameregistration.com MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REQUEST_TIMEOUT_MS | No | Timeout for each upstream attempt (in milliseconds). | 15000 |
| DOMAIN_CACHE_TTL_MS | No | How long successful results remain in memory (in milliseconds). | 60000 |
| UPSTREAM_BATCH_SIZE | No | Maximum domains in each sequential upstream request. | 250 |
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 |
|---|---|
| search_domainsA | Bulk domain name search, maximum 1,000 per call. Returns available, taken, noInfo, and aftermarket groups. |
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
Only one tool exists, so there is no ambiguity or risk of misselection.
The single tool uses a clear verb_noun pattern (search_domains), which is consistent and readable.
With only one tool, the server feels very thin for a domain registration service, lacking many expected operations.
The tool surface is severely incomplete, covering only search while missing registration, transfer, DNS management, and other core domain operations.