DomainDetails 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| domain_lookupA | Look up domain information using RDAP protocol with WHOIS fallback. Provides comprehensive domain registration details, nameservers, contacts, and status information. |
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. The tool's purpose is clearly stated and unique.
The tool name 'domain_lookup' follows a clear, readable pattern and is appropriate for its function. With a single tool, there is no inconsistency.
The server is focused on domain details lookup, and a single tool adequately covers this narrow scope. While the typical range is 3-15, the simplicity of the purpose justifies the minimal count, making it slightly under but reasonable.
The tool provides comprehensive domain information via RDAP with WHOIS fallback, covering registration, nameservers, contacts, and status. There are no obvious missing operations for a lookup-only service.