Name MCP server

Which servers in the official MCP registry are Name's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to Name

Whose server it is

Registry nameai.name/nameai-mcpverified in the MCP registry

The registry name sits under name.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-12

Stateanswerschecked 2026-10-12
Tools4
Server calls itselfnameai-mcp
Server version1.0.0
Protocol version2025-06-18

On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 529 ms.

Tools it offers4 tools · read 2026-10-12

search_domain
Check whether a domain is available and, for the same label, whether its common alternate TLDs are too (e.g. querying "acme.com" also returns "acme.ai", "acme.io", ...). Backed by POST /api/domain/search — public, no auth required…
whois_lookup
Look up WHOIS/RDAP registration details for a domain: registrar, registrant, creation/expiration dates, nameservers. Backed by POST /api/tools/whois — public, no auth required, but rate limited by name.ai to 10 lookups per day per caller…
tld_registration_price
Get the current USD price for a domain-lifecycle operation on a TLD (new registration, transfer-in, renewal, or restore from redemption). Backed by GET /api/pricing/tld — public, no auth required. This is name.ai's own registration…
tld_requirements
Get registration requirements for a TLD: allowed registration period range, whether an organization is required, allowed registrant countries, nameserver rules, and similar registry policy. Backed by GET /api/tlds/{tld}/metadata — public…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

OpenAPI spec

10 paths, read 2026-10-12. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.