DomainRoc MCP 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainA | Check a single domain's confirmed availability and first-year USDT preview price. Input: a fully-qualified DNS domain, e.g. example.com (IDN in xn-- ASCII form). Returns unknown if upstream fails, restricts the domain, or requires manual review. Does not create orders, charge accounts, or register domains. |
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 is present, so there is no overlap or possibility of misselection. Its purpose is clearly stated as checking a single domain's availability and price.
The single tool name check_domain follows a clear verb_noun convention. With only one tool, there is no inconsistency in style or pattern.
The server has only one tool, which is thin even for a focused domain-availability service. It is arguably sufficient for the narrow stated purpose, but the surface feels under-scoped.
The core single-domain availability check is covered, but notable adjacent operations such as bulk checks, TLD exploration, or richer domain lookup are absent. The tool explicitly excludes order creation and registration, so lifecycle coverage is intentionally incomplete.