Domain Checker
Enables checking domain name availability using WHOIS lookups and DNS resolution. Supports both single and batch domain checking with detailed availability analysis.
README
Remote MCP Server Template
This is a template for creating remote MCP servers that can be deployed to DigitalOcean App Platform. Remote MCP servers allow you to deploy MCP functionality to the cloud and use it from any MCP-compatible client (Claude Desktop, Cursor, Windsurf, etc.) without local installation.
This Specific Implementation: Domain Checker
This template demonstrates a domain availability checker that uses WHOIS lookups and DNS resolution. Built with the modern FastMCP framework for reliable domain availability checking.
Deploy this Remote MCP Server to DigitalOcean
Quick Start (1-Click Deploy)
- Deploy to DigitalOcean using the button above
- Get your deployed URL from DigitalOcean (e.g.,
https://your-app.ondigitalocean.app) - Add to your MCP client using the URL +
/mcpendpoint
Features
- ✅ Dual Verification: Uses both WHOIS and DNS resolution for accurate results
- 🚀 Async Operations: Non-blocking operations with proper timeout handling
- 📊 Batch Processing: Check multiple domains concurrently
- 🔍 Detailed Analysis: Provides comprehensive availability information
Using Your Remote MCP Server
Option 1: Use Your Deployed Remote MCP Server (Recommended)
After deploying to DigitalOcean, add your server URL to your MCP client:
{
"mcpServers": {
"domain-checker": {
"url": "https://YOUR-APP-NAME.ondigitalocean.app/mcp",
"description": "Check domain availability"
}
}
}
Replace YOUR-APP-NAME with your actual DigitalOcean app name.
Option 2: With FastMCP Development Tools
# Make sure your virtual environment is activated
fastmcp dev local-domain-checker.py
Option 3: Configure Local MCP Server
This MCP server works with Claude Desktop, Cursor, Windsurf, and other MCP-compatible applications.
Configuration Locations
- Claude Desktop:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Cursor:
- macOS:
~/Library/Application Support/Cursor/cursor_desktop_config.json - Windows:
%APPDATA%\Cursor\cursor_desktop_config.json
- macOS:
- Windsurf:
- macOS:
~/Library/Application Support/Windsurf/windsurf_desktop_config.json - Windows:
%APPDATA%\Windsurf\windsurf_desktop_config.json
- macOS:
Add the following configuration to the appropriate file, making sure to point to your virtual environment:
{
"mcpServers": {
"domain-checker": {
"command": "/path/to/your/venv/bin/python",
"args": ["/path/to/your/local-domain-checker.py"]
}
}
}
Important:
- Replace paths with the actual paths to your virtual environment and domain checker directory
- Use
local-domain-checker.pyfor local development (it has simpler configuration without port/host settings) domain-checker.pyis configured for remote deployment with additional parameters
Installation (For Local Use)
Prerequisites
- Python 3.8 or higher
- pip package manager
Setup
-
Clone the repository
git clone https://github.com/ajot/domain-checker-mcp-server.git cd domain-checker-mcp-server -
Create and activate a virtual environment (recommended)
python -m venv venv # On macOS/Linux source venv/bin/activate # On Windows venv\Scripts\activate -
Install dependencies
pip install -r requirements.txt
Deploy to DigitalOcean App Platform
This MCP server can be deployed as a remote MCP server on DigitalOcean App Platform.
Prerequisites
- A DigitalOcean account
- The doctl command-line tool (optional)
- Git repository with your code
Deployment Steps
-
Push your code to a Git repository Make sure all your changes are committed and pushed to a GitHub, GitLab, or Bitbucket repository.
-
Create a new App on DigitalOcean App Platform
- Go to the DigitalOcean App Platform dashboard
- Click "Create App" and select your Git repository
- Select the branch you want to deploy
- Choose "Python" as the environment
-
Configure the App
- Set the source directory to
/ - Set the run command to:
python domain-checker.py - Set the environment variable:
PORT=8080 - Set HTTP port to 8080
- Set the source directory to
-
Deploy the App
- Click "Deploy to Production"
- Wait for the build and deployment to complete
-
Configure as Remote MCP Once deployed, you can use the app URL as a remote MCP server in your MCP-compatible applications:
{ "mcpServers": { "domain-checker": { "url": "https://your-app-name.ondigitalocean.app/mcp", "description": "Check domain name availability" } } }
Updating Your Deployment
To update your deployed app, simply push changes to your Git repository. DigitalOcean App Platform will automatically build and deploy the new version.
Usage Examples
Check Single Domain
"Check if myawesome-startup.com is available"
Check Multiple Domains
"Check availability for these domains: mycompany.com, mycompany.net, mycompany.org"
Understanding Results
Availability Status
- ✅ LIKELY AVAILABLE: Domain appears to be unregistered and available
- ❌ NOT AVAILABLE: Domain is registered and not available
- ❓ UNCLEAR: Mixed signals - manual verification recommended
Sample Output
Domain: example-startup.com
Status: ✅ LIKELY AVAILABLE
WHOIS Check: Available
DNS Resolution: Not resolving
Details:
{
"whois": {
"available": true,
"reason": "WHOIS parser error: No match for domain"
},
"dns": {
"resolvable": false,
"reason": "Domain does not resolve (NXDOMAIN)"
}
}
Troubleshooting
Common Issues
1. Import Errors
- Make sure your virtual environment is activated
- Verify all dependencies are installed:
pip install -r requirements.txt
2. Timeout Issues
- Some WHOIS servers have rate limits
- Network connectivity issues can cause timeouts
3. DigitalOcean Deployment Issues
- Check that the port is set to 8080 in both the code and the App Platform configuration
- Verify that all dependencies are in requirements.txt
- Check the deployment logs for any error messages
Disclaimer: This tool provides estimates of domain availability. Always verify availability through official domain registrars before making any purchase decisions.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.