Truffle Domain Checker MCP Server
A Model Context Protocol (MCP) server that provides domain availability checking capabilities. Perfect for product name research and brand validation.
Features
- Single Domain Check: Check availability of a specific domain
- Batch Domain Check: Check multiple domains simultaneously
- Domain Variations: Check a base name across multiple TLDs
- Dual Verification: Uses both WHOIS lookups and DNS resolution
- Async Operations: Non-blocking concurrent domain checks
Installation
Using uvx (recommended)
uvx --from git+https://github.com/truffle-ai/mcp-servers --subdirectory src/domain-checker truffle-domain-checker-mcp
Using uv
uv add git+https://github.com/truffle-ai/mcp-servers --subdirectory src/domain-checker
From source
git clone https://github.com/truffle-ai/mcp-servers.git
cd mcp-servers/src/domain-checker
uv sync
uv run truffle-domain-checker-mcp
Usage
The server provides three main tools:
check_domain(domain: str)
Check if a single domain is available for registration.
check_multiple_domains(domains: List[str])
Check availability for multiple domains at once. Great for comparing product name options.
check_domain_variations(base_name: str, extensions: List[str] = None)
Check a base name across multiple TLD extensions (.com, .net, .org, .io, .app, .dev, .tech by default).
Domain Status Indicators
- ✅ LIKELY AVAILABLE: Domain appears to be unregistered
- ❌ NOT AVAILABLE: Domain is registered and in use
- ❓ UNCLEAR: Mixed signals, manual verification recommended
Configuration with MCP Clients
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"domain-checker": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/truffle-ai/mcp-servers",
"--subdirectory",
"src/domain-checker",
"truffle-domain-checker-mcp"
],
"env": {
"MCP_TRANSPORT": "stdio"
}
}
}
}
Saiki
Add to your Saiki configuration:
mcp_servers:
- name: domain-checker
command: uvx
args:
- --from
- git+https://github.com/truffle-ai/mcp-servers
- --subdirectory
- src/domain-checker
- truffle-domain-checker-mcp
env:
MCP_TRANSPORT: stdio
Examples
Single Domain Check
User: Is myawesomeapp.com available?
Assistant: [Uses check_domain("myawesomeapp.com")]
Multiple Domain Check
User: Check availability for myapp.com, myapp.io, and myapp.dev
Assistant: [Uses check_multiple_domains(["myapp.com", "myapp.io", "myapp.dev"])]
Domain Variations
User: Check all major extensions for "brandname"
Assistant: [Uses check_domain_variations("brandname")]
Dependencies
fastmcp>=0.1.0- FastMCP frameworkpython-whois>=0.8.0- WHOIS lookupsdnspython>=2.4.0- DNS resolutionuvicorn>=0.23.0- HTTP server support
License
MIT - See LICENSE for details.
Contributing
Contributions welcome! Please see CONTRIBUTING.md for guidelines.
Metadata
Release files for truffle-domain-checker-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| truffle_domain_checker_mcp-1.0.0.tar.gz | 5.9 kB | Without provenance | Details |
Release files / truffle_domain_checker_mcp-1.0.0.tar.gz
| Download URL | truffle_domain_checker_mcp-1.0.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cdcf4a58bebc4a0a729551c5360af92b0893e3fc9b25b3179cda007f8bfe3b7b
|
|
BLAKE2b-256 checksum How to use checksums |
9ecf4365a4f323dbcda02fd562a40cdbe78093281ca7100ecb5d44f3cacac85c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.21
|
Security for truffle-domain-checker-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.