domain-check-mcp
by stucchi
README.md
# domain-check-mcp
[](https://pypi.org/project/domain-check-mcp/)
[](https://opensource.org/licenses/MIT)
[](https://www.python.org/)

[](https://modelcontextprotocol.io)
[](https://claude.ai/)
[](https://github.com/stucchi/domain-check-mcp/stargazers)
[](https://github.com/stucchi/domain-check-mcp/issues)
MCP server for checking domain name availability. Supports 500+ TLDs via RDAP, with WHOIS fallback for .de and .cn.
## Installation
```bash
uvx domain-check-mcp
```
## Usage in .mcp.json
```json
{
"mcpServers": {
"domain-check": {
"command": "uvx",
"args": ["domain-check-mcp"]
}
}
}
```
## Tools
- **check_domain** — Check if a domain name is available for registration
### Example
```
check_domain("example.com")
```
Returns:
```json
{
"domain": "example.com",
"available": false,
"status": "registered"
}
```
## Supported TLDs
### Via RDAP (500+)
All major gTLDs and many ccTLDs with RDAP support, sourced from the [IANA RDAP Bootstrap](https://data.iana.org/rdap/dns.json):
.com, .net, .org, .info, .app, .dev, .io, .xyz, .site, .shop, .uk, .fr, .nl, .pl, .consulting, .cloud, .tech, .blog, .store, .online, and [many more](src/domain_engine/tld_registry.py).
### Via WHOIS
| TLD | WHOIS Server |
|-----|-------------|
| .de | whois.denic.de |
| .cn | whois.cnnic.cn |
| .fj | www.whois.fj |
| .gs | whois.nic.gs |
| .bayern | whois.nic.bayern |
| .cat | whois.nic.cat |
| .eus | whois.nic.eus |
| .radio | whois.nic.radio |
| .scot | whois.nic.scot |
| .sport | whois.nic.sport |
## How it works
1. Extracts the TLD from the domain name
2. Routes to the appropriate adapter (RDAP or WHOIS)
3. **RDAP**: HTTP lookup — 404 means available, 200 means registered
4. **WHOIS**: TCP port 43 lookup — pattern matching on the response
5. Returns a structured result with availability status
## Development
```bash
git clone https://github.com/stucchi/domain-check-mcp.git
cd domain-check-mcp
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
pytest
```
## License
MIT
<!-- mcp-name: io.github.stucchi/domain-check -->
TDQS
A3.6/5.0
Scored across 2 tools
Disambiguation5/5
The two tools are clearly distinct: one checks a single domain, the other checks multiple domains in bulk. There is no overlap in purpose.
Naming Consistency5/5
Both tools follow the verb_noun pattern (check_domain, check_domains) consistently, with the plural form appropriately indicating bulk operation.
Tool Count4/5
With 2 tools, the server is minimal but appropriately scoped for its purpose—checking domain availability. The count is slightly low but reasonable for a focused utility.
Completeness4/5
The server covers both single and bulk domain availability checks, which is the core functionality. No major gaps are apparent, though it does not offer additional details like whois data.
Maintenance
ActivityInactive
ResponsivenessNo issues