About Name.ai MCP Server
Name.ai MCP Server wraps name.ai's public APIs as read-only tools for users looking up domain information. It covers domain availability, WHOIS, TLD registration prices, and registration requirements.
Key features
- 01Search domains and check availability
- 02Look up WHOIS information
- 03View TLD registration prices
- 04Check TLD registration requirements
Use cases
- 01Check whether a candidate domain is available
- 02Look up domain registration details
- 03Compare prices and requirements across TLDs
MCP support
This remote MCP server exposes name.ai's public API tools over Streamable HTTP, with MCP clients connecting to the `/mcp` endpoint.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.name.ai/mcpclaude mcp add --transport http ai-name-nameai https://mcp.name.ai/mcp{"mcpServers":{"ai-name-nameai":{"type":"http","url":"https://mcp.name.ai/mcp"}}}Open in Cursor{"servers":{"ai-name-nameai":{"type":"http","url":"https://mcp.name.ai/mcp"}}}Open in VS Code{"mcpServers":{"ai-name-nameai":{"type":"http","url":"https://mcp.name.ai/mcp"}}}{"mcpServers":{"ai-name-nameai":{"serverUrl":"https://mcp.name.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
4| Parameter | Type | Required | Description |
|---|---|---|---|
| domain | string | Yes | |
| include_alternates | boolean | No |
Details
From the project READMEnameai-mcp
A remote MCP server exposing a handful of name.ai's public, no-auth-required APIs as tools: domain search/availability, WHOIS lookup, TLD registration pricing, and TLD requirements. See src/nameai_mcp/server.py for the tool definitions and src/nameai_mcp/nameai_client.py for the HTTP client that talks to name.ai.
Endpoints
GET /health— health check.POST /mcp(andGET /mcpfor the SSE stream) — the MCP streamable-http endpoint. This is the URL an MCP client/host connects to.
Configuration
NAMEAI_API_BASE_URL— base URL of the name.ai API this server calls. Defaults tohttps://name.ai.HOST/PORT— bind address for the server itself. Default0.0.0.0:8000.
Local development
uv sync
uv run uvicorn nameai_mcp.app:app --reload
Docker
docker build -t nameai-mcp .
docker run -p 8000:8000 nameai-mcp
The image runs nameai-mcp (the main() entry point in
src/nameai_mcp/__init__.py), which reads
HOST/PORT from the environment — pass -e PORT=... if your platform
injects a different port.
Deploying
Any host that can run the Docker image works. It is deployed through Coolify
on the Hetzner server and served at https://mcp.name.ai/mcp
(streamable-http), with Traefik terminating TLS. The original hostname,
https://nameai-mcp.h.namekart.com/mcp, still routes to the same container, so
client configs written against it keep working.
mcp.name.ai is a DNS-only A record to the Hetzner box. It exists because
scanners and MCP tooling look for a server at mcp.<domain> instead of reading
the URL out of a manifest — ora's scanner was watched, in this container's own
access log, never dialling the manifest's mcpUrl during a scan. Adding a
hostname needs two things besides DNS: the domain on the Coolify app, and the
host appended to MCP_ALLOWED_HOSTS, without which the SDK's DNS-rebinding
guard answers it with 421.
The server calls the public API at NAMEAI_API_BASE_URL, default
https://name.ai. Since name.ai moved to Hetzner that resolves to the same
host this container runs on, so the calls leave the container, reach the
host's own public IP, and come back in through Traefik. That hairpin works
here and is left in place deliberately: talking to the API exactly the way an
outside client would is the point of this server.
Being reachable isn't the same as being discovered — and that part is done.
name.ai advertises this server in four places:
https://name.ai/.well-known/mcp.json— manifesthttps://name.ai/.well-known/mcp/server-card.json— server cardhttps://name.ai/llms.txt— in both the endpoint list and the tool guidance- the MCP Registry, namespace
ai.name, domain-verified
All four live in the nameaiv1 repo. If the deployed URL changes, they change with it — otherwise agents keep being pointed at the old one.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.