domain-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_domainsA | Search for domain name suggestions and check their availability. Given a query (e.g. "devstroop" or "acme coffee"), returns matching domain names across many TLDs (.com, .io, .dev, etc.) with availability status. No API key required — uses RDAP + domainr.com. |
| check_domainA | Check the availability and detailed status of a specific domain name. Returns: available/taken, registrar, creation/expiration dates, nameservers, and RDAP status flags. No API key required — uses RDAP + DNS. |
| check_multiple_domainsA | Check availability of multiple domain names at once. Returns a comparison table with availability, registrar, expiry, and details. Useful for comparing alternatives (e.g. devstroop.com vs devstroop.io vs devstroop.dev). Maximum 20 domains per request. No API key required. |
| whois_lookupA | Perform a WHOIS lookup for a domain name. Returns registrar, registrant, creation/expiration dates, nameservers, status, and abuse contacts. Queries real WHOIS servers directly via TCP port 43 — no API key required. Set raw=true to get the full raw WHOIS text. |
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 4 tools
Each tool has a clearly distinct purpose: domain search suggestions, single availability check, bulk availability check, and WHOIS lookup. Even though check_domain and whois_lookup both return registration details, one focuses on availability and RDAP while the other provides full WHOIS data, avoiding confusion.
All tool names follow a consistent verb_noun pattern with snake_case: search_domains, check_domain, check_multiple_domains, whois_lookup. The naming is predictable and uniform.
With 4 tools, the server is well-scoped for domain search and lookup operations. Each tool serves a core function without redundancy, fitting the typical 3-15 tool range.
The tool set covers search, single and bulk availability checks, and detailed WHOIS data—covering the main domain lookup needs. A minor gap is the absence of DNS record lookup, but for a domain availability and WHOIS server, this is acceptable.