MCP server

Use Namester from your AI assistant: ask for names you can register, check availability and search expired, auction and for-sale domains.

Connect

Create an API key, then add the server to your MCP client. The key is sent as a Bearer token. Create an API key

Endpoint: https://new.namester.ai/api/mcp
Transport: Streamable HTTP
Auth: Authorization: Bearer sk_…

Claude Code

claude mcp add --transport http namester https://new.namester.ai/api/mcp \
  --header "Authorization: Bearer sk_…"

Claude Desktop, Cursor and other JSON configs

{
  "mcpServers": {
    "namester": {
      "type": "http",
      "url": "https://new.namester.ai/api/mcp",
      "headers": { "Authorization": "Bearer sk_…" }
    }
  }
}

Keep the key in your local client config only — never in a shared repository. Revoke it under Settings → API keys if it leaks.

Tools

suggest_names
Describe a project; get AI name ideas that were checked live and are available to register, plus matching domains for sale. Uses one Finder search.
check_availability
Live registration check for up to 50 names (cache, DNS, registry RDAP, registrar price).
search_domains
Expired, deleted, auction, closeout, buy-now and pending-delete domains with the same filters as the Domains page.
get_domain
Full profile of one domain: current offers, score breakdown, price history, comparable sales and registration details.

Try asking

“Find me an available .com for a meal-planning app for busy parents.”
“Are brewly.com, brewly.ai and brewly.io available?”
“Show .com auctions under $100 ending in the next 24 hours.”

Plans and limits

Needs a paid plan with API access. Every MCP request counts toward the plan’s API allowance (Pro 25,000 / Max 100,000 requests per hour).
suggest_names and check_availability also use the Finder’s daily quota, the same as searches on the website.
Prefer plain HTTP? The same data is available from the REST API: API