---
title: "Name.ai MCP Server — Model Context Protocol Endpoint and Tools"
description: "Connect the Name.ai MCP server to Claude, Cursor or any Model Context Protocol client: domain search and availability, WHOIS lookup, and TLD pricing and requirements as MCP tools over Streamable HTTP. No install, no API key."
url: https://name-stage.vps4.auctionhacker.com/developers/mcp
---

[Name.ai developer portal](https://name-stage.vps4.auctionhacker.com/developers) / MCP

# Name.ai MCP server

The Name.ai MCP server exposes domain search and availability, WHOIS lookup, and TLD pricing and requirements as Model Context Protocol tools. It is remote and hosted — no install, no API key — and speaks Streamable HTTP, so any MCP client can use it: Claude Code, Claude Desktop, Cursor, and others. Signing in via OAuth is optional and additionally unlocks real marketplace prices on domain searches.

## Endpoint

```
https://mcp.name.ai/mcp
```

Discoverable without reading this page: the manifest is at [/.well-known/mcp.json](https://name-stage.vps4.auctionhacker.com/.well-known/mcp.json) (also served extensionless at [/.well-known/mcp](https://name-stage.vps4.auctionhacker.com/.well-known/mcp)) and the server card at [/.well-known/mcp/server-card.json](https://name-stage.vps4.auctionhacker.com/.well-known/mcp/server-card.json). The server is listed in the [official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=ai.name/nameai-mcp) under the domain-verified namespace `ai.name`, and its source — with `AGENTS.md` and the `plugin.json` Agent Plugins manifest — is at [github.com/namekart/nameai\_mcp](https://github.com/namekart/nameai_mcp).

## Add it to an MCP client

```
{
  "mcpServers": {
    "name-ai": {
      "type": "http",
      "url": "https://mcp.name.ai/mcp"
    }
  }
}
```

Or with the Claude Code CLI:

```
claude mcp add --transport http name-ai https://mcp.name.ai/mcp
```

## Tools

search\_domain

Check whether a domain is available, with common alternate-TLD suggestions for the same label.

whois\_lookup

WHOIS/RDAP registration details for a domain: registrar, registrant, dates, nameservers.

tld\_registration\_price

Current USD price for registering, transferring, renewing or restoring a domain on a TLD.

tld\_requirements

Registration requirements for a TLD: period range, organization rules, nameserver rules.

## In-page WebMCP

The same public, read-only capabilities are also registered in the browser via the WebMCP draft API (`document.modelContext`) on pages where they fit — home, search, bulk search, pricing, TLD guides, market/buy, WHOIS, and a few non-AI free tools. Browser agents can call them without leaving the tab. Landers and customer-domain pages send `Permissions-Policy: tools=()` so nothing registers there. WebMCP may list a few extras the remote MCP server does not:

check\_many\_domains

Batch up to 20 domain availability checks in one call (search + bulk search pages).

browse\_marketplace

Browse aftermarket listings (market and buy pages). Seller text is marked untrusted.

sitemap\_finder / sitemap\_url\_extractor / webpage\_to\_markdown

Selected non-AI free tools, registered only on that tool’s own /tools/… page.

## Source and related resources

-   [github.com/namekart/nameai\_mcp](https://github.com/namekart/nameai_mcp) — server source, `AGENTS.md`, and the agent plugin manifest.
-   [Name.ai API docs](https://name-stage.vps4.auctionhacker.com/developers/api) — the same capabilities as plain REST, for clients not speaking MCP.
-   [Name.ai API authentication](https://name-stage.vps4.auctionhacker.com/developers/auth) — the optional OAuth 2.1 flow.

---

Markdown representation of https://name-stage.vps4.auctionhacker.com/developers/mcp. The same URL returns HTML to any client that asks for `text/html`. Site map for agents: https://name-stage.vps4.auctionhacker.com/llms.txt