Domain Checker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server (only used in test mode). | 6005 |
| WHOISJSON_API_KEY | Yes | Your WhoisJSON API key for checking domain availability. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainB | Check if a domain name is available for registration. Returns availability status and registration details if the domain is taken. |
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 possibility of confusion between tools. Its purpose is clearly defined and distinct.
With a single tool, there is no inconsistency in naming. The name 'check_domain' is descriptive and follows a clear verb_noun pattern.
The server has only one tool, which is borderline for a domain checker. While it serves the core function, additional tools for batch checks or WHOIS could be expected.
The tool covers checking domain availability, but lacks supplementary operations like bulk checks or WHOIS details, which are common in domain checking services.