Get the FREE Ultimate OpenClaw Setup Guide →

domain-checker

A Model Context Protocol (MCP) server that checks domain name availability using WHOIS lookups and DNS resolution

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio ajot-domain-checker-mcp-server python domain-checker.py \
  --env PORT="8080" \
  --env LOG_LEVEL="INFO"

How to use

This MCP server implements a domain availability checker that uses WHOIS lookups and DNS resolution to determine if a domain name is likely available. It is built with the FastMCP framework to provide a responsive, asynchronous experience and supports batch processing for checking multiple domains at once. You can run it locally using Python and integrate it into any MCP-compatible client or remote MCP workflow to query domain availability and receive structured results that include WHOIS and DNS analysis along with a combined status. The local script domain-checker.py is designed for development, while the remote deployment exposes an HTTP endpoint for use by MCP-enabled apps.

How to install

Prerequisites:

  • Python 3.8 or higher
  • pip (comes with Python)
  • Git

Setup steps:

  1. Clone the repository and navigate to the project directory:
git clone https://github.com/ajot/domain-checker-mcp-server.git
cd domain-checker-mcp-server
  1. Create and activate a virtual environment (recommended):
python -m venv venv
# macOS/Linux
source venv/bin/activate
# Windows
venv\Scripts\activate
  1. Install dependencies:
pip install -r requirements.txt
  1. Run the local domain checker:
python domain-checker.py
  1. If you plan to deploy remotely (e.g., DigitalOcean App Platform), configure the run command to use Python with the domain-checker.py script and ensure PORT is set (commonly PORT=8080).

Additional notes

Tips and common notes:

  • If running locally, ensure your virtual environment is active and dependencies from requirements.txt are installed.
  • When deploying remotely, the App Platform or host may require you to expose port 8080 and set PORT=8080 in environment variables.
  • The remote MCP configuration example includes a URL and description; replace with your actual deployed endpoint when integrating.
  • For debugging WHOIS lookups or DNS resolution, you may need network access and permissions to query external services; consider rate limits and implement retries as needed.
  • This tool returns structured results including an overall availability status and detailed sub-results for WHOIS and DNS checks.

Related MCP Servers

Sponsor this space

Reach thousands of developers