Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.name.ai/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http ai.name-nameai-mcp https://mcp.name.ai/mcpRun in a terminal.
{ "mcpServers": { "ai.name-nameai-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.name.ai/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
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.
Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.
GET /health — health check.POST /mcp (and GET /mcp for the SSE stream) — the MCP streamable-http
endpoint. This is the URL an MCP client/host connects to.NAMEAI_API_BASE_URL — base URL of the name.ai API this server calls.
Defaults to https://name.ai.HOST / PORT — bind address for the server itself. Default 0.0.0.0:8000.uv sync
uv run uvicorn nameai_mcp.app:app --reload
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.
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 guidanceai.name, domain-verifiedAll four live in the nameaiv1 repo. If the deployed URL changes, they change with it — otherwise agents keep being pointed at the old one.
© 2026 MCP Directory.
Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.
{ "mcpServers": { "ai.name-nameai-mcp": { "url": "https://mcp.name.ai/mcp", "headers": {} } }}4 tools
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Name.ai MCP Server is reached over HTTP.
Last checked 2026-10-19. Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.