- Home
- MCP servers
- FastDomainCheck
FastDomainCheck
- go
34
GitHub Stars
go
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"bingal-fastdomaincheck-mcp-server": {
"command": "/path/to/FastDomainCheck-MCP-Server",
"args": []
}
}
}FastDomainCheck MCP Server provides a Model Context Protocol implementation that lets AI tools securely query bulk domain registration status. It supports bulk checks, dual verification via WHOIS and DNS, IDN handling, and concise outputs, making it practical for automations that need to assess domain availability at scale.
How to use
You use this MCP server by connecting your MCP client to the provided local or remote server endpoint and issuing the check_domains tool to verify multiple domains in one request. The server runs as a local or remote process and returns a structured result indicating whether each domain is registered or available. You can rely on dual verification (WHOIS primary with DNS fallback) to improve accuracy, and you can provide IDNs if needed.
How to install
Prerequisites you need before installing this MCP server are a Go 1.16+ toolchain and network access for WHOIS and DNS queries.
Option 1: Download the prebuilt binary (recommended for quick start) and run it locally.
-
Download the binary from the release page.
-
Make the binary executable on macOS/Linux.
-
Run the server locally (the exact start command depends on your platform and setup). For a Unix-like system, you would typically execute the binary you downloaded.
Additional configuration and runtime details
MCP server settings for Claude Desktop show how to register the FastDomainCheck MCP Server as a stdio-based process. You can configure either a macOS/Linux setup or a Windows setup.
Tool documentation and usage
The FastDomainCheck MCP Server provides a tool named check_domains to verify registration status for multiple domain names. You supply a list of domains (up to 50 per request, each up to 255 characters). The output indicates which domains are registered.
Security and reliability notes
Input validation is performed to prevent empty lists or invalid domain names. If a request cannot be processed, a clear error is returned. The server prefers WHOIS verification with DNS fallback and uses reasonable timeouts for network operations.
Examples and expectations
A typical response maps domain names to a boolean indicating registration status, e.g. registered: true if the domain exists, or registered: false if it is available.
Available tools
check_domains
Check registration status for multiple domain names. Accepts an array of up to 50 domains (each up to 255 chars) and returns a results object with each domain's registered boolean.