playbooks

home / mcp / namechecker mcp server

NameChecker MCP Server

Provides real-time domain availability checks and RFC-compliant domain syntax validation for AI assistants via the MCP protocol.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "emrekb-namechecker-mcp": {
      "url": "https://mcp.example.com/mcp",
      "headers": {
        "LOG_LEVEL": "INFO"
      }
    }
  }
}

The NameChecker MCP Server lets AI assistants verify domain name availability and validate domain syntax in real time. It provides practical integration through the MCP protocol, enabling smooth interaction with AI copilots as you check domains during conversations or automated workflows.

How to use

You connect to the NameChecker MCP Server via an MCP client and choose either the stdio transport for local runs or the SSE transport for networked usage. Use the available tools to check a domain’s availability or to validate its syntax. When you check availability, you provide a domain and an optional top-level domain. When you validate syntax, you get a detailed result describing the domain structure and validity.

How to install

Prerequisites you need before installation are Python 3.9 or higher and pip. Ensure Python is in your system PATH.

Install from source and set up the development environment with these steps:

# Clone the project
git clone <repository-url>
cd namechecker-mcp

# Install in development mode
pip install -e ".[dev]"

Additional notes and configuration

You can run the server in stdio mode for local development or in SSE mode to expose an HTTP endpoint for clients. The stdio run uses the Python interpreter to execute the main script, while the SSE run opens a socket on port 8000 and serves messages at the designated endpoint.

Example run commands:

# Run with default stdio transport
python main.py

# Run with SSE transport on port 8000
python main.py --transport sse --port 8000

# Run with custom settings
python main.py --transport stdio --log-level DEBUG --timeout 60

Configuration and MCP client setup

To use this server with an MCP client, you can configure it in your MCP setup to connect via stdio or SSE. The following examples show how you can integrate the server into common MCP clients.

Stdio transport configuration (local, command-based):

{
  "name": "namechecker",
  "transport": {
    "type": "stdio",
    "command": "python",
    "args": ["main.py"]
  }
}

SSE transport configuration (network endpoint)

If you prefer an HTTP endpoint for MCP clients, configure the SSE transport with a URL that serves messages.

{
  "name": "namechecker",
  "transport": {
    "type": "sse",
    "url": "http://localhost:8000/messages"
  }
}

Security and environment

Limit access to the SSE endpoint to trusted clients when deploying in production. You can set logging levels through environment variables if your deployment workflow supports it.

# Example environment for logging level when running in certain environments
LOG_LEVEL=INFO

Available tools

check_domain_availability

Checks if a domain name is available for registration. Returns a boolean indicating availability.

validate_domain_syntax

Validates domain name syntax according to RFC standards. Returns a structured result detailing validity and components.