domain-rdap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport protocol for the MCP server. Set to 'http' for self-hosting over HTTP. | |
| DOMAIN_LOCAL_DEV | No | Set to '1' to enable local development mode. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainA | Check whether a domain name is registered, using real-time RDAP data (the IETF-standardized successor to WHOIS). Use for "is domain-x.com available/registered", "who is domain-x.com registered with", or "when does domain-x.com expire" style questions.
If the domain is NOT registered, returns If the domain IS registered, returns For obviously malformed input (not a domain -- e.g. missing a dot, has
spaces, or includes a protocol like "https://"), returns a clean
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sponsored_card | |
| result_widget_check_domain |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined.
The single tool 'check_domain' follows a clear verb_noun convention, which is consistent and descriptive.
A single tool is perfectly scoped for a server dedicated to RDAP domain lookups. It covers the entire domain without unnecessary bloat.
The tool provides comprehensive domain information: registration status, dates, and registrar. It fully addresses the primary use cases for RDAP queries.