Domain Availability Checker MCP
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainA | Check if a domain is available for registration. Supported TLDs: .com, .net |
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
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is entirely clear and distinct.
The single tool name follows a clear verb_noun convention ('check_domain'). With only one tool, naming consistency is inherently maintained.
A single tool is on the borderline for a server. While it serves the narrow scope of checking domain availability, the surface feels thin with no supporting tools for related operations like bulk checks or WHOIS lookups.
For the stated purpose of checking domain availability, the tool fully covers the core operation. There are no missing lifecycle steps or dead ends for this narrow domain.