nameai-mcp

MCP serverSearch

nameai-mcp lets your AI check whether domain names are available before you commit to one. It can look up WHOIS registration details, compare pricing across top-level domains, and check the rules each registry applies. Useful when you're naming a project, business, or product and want answers without leaving your conversation.

Use nameai-mcp in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add nameai-mcp and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use nameai-mcp to search domain

Details

Available today. Use it from your connected AI after setup.

Add the integration, then ask your AI something like 'is namekart.com available and what would similar names cost?' It works read-only, so it can look things up but won't register anything for you.

nameai-mcpStart free

What your AI can do with it

  • Check if a domain name is available to register
  • Look up WHOIS details for any domain
  • Compare registration prices across different top-level domains
  • Check registry rules before you buy
  • Search across many TLDs at once

Install nameai-mcp

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user nameai-mcp 'https://mcp.name.ai/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://mcp.name.ai/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=nameai-mcp&config=eyJ1cmwiOiJodHRwczovL21jcC5uYW1lLmFpL21jcCJ9

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://mcp.name.ai/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add nameai-mcp --url 'https://mcp.name.ai/mcp'

    Run it once, then sign in with codex mcp login nameai-mcp if the server asks for an account.

From the project's README

As published by namekart/nameai_mcp in README.md.

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 (and GET /mcp for 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 to https://name.ai.
  • HOST / PORT — bind address for the server itself. Default 0.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 — manifest
  • https://name.ai/.well-known/mcp/server-card.json — server card
  • https://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.

Tools it offers (4)

What this server listed when Ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.

  • search_domain
  • whois_lookup
  • tld_registration_price
  • tld_requirements

Signals

Last commit
Sep 2026
Advanced
Delivery
nameai-mcp MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
ai-name-nameai-mcp
Source
github.com/namekart/nameai_mcp
Hosted endpoint
https://mcp.name.ai/mcp