NameBeta MCP server
NameBeta runs a remote Model Context Protocol (MCP) server. Connect it to Claude, ChatGPT, Codex, VS Code, Cursor or any other MCP client, and your assistant can check whether a domain is available, compare registrar prices, suggest names, and look up WHOIS and DNS records — with the same live data as namebeta.com. Tools lists what each of the five tools does.
Connect in a minute
Nothing runs on your machine. Every client connects to the same URL:
https://namebeta.com/api/mcp
- Add the URL to your client as a remote MCP server. Leave any client ID, secret or token fields empty.
- Sign in with your NameBeta account when the client asks. The sign-in page lets you create an account if you do not have one.
- Ask your assistant about a domain.
Step-by-step pages: Claude.ai, Claude Code, ChatGPT, Codex, VS Code, Cursor, Gemini CLI, Windsurf and other clients. Connect a client shows which of them we have tested, and which need a client ID from us first.
Quota
Tool calls count against your NameBeta plan. Quotas explains how they are counted, the limits of each plan and what happens when you reach one.
Service level
The NameBeta MCP server is provided as is, without a service level agreement. We do not commit to any availability, uptime, response time or support response time, and tools, quotas and response fields may change. Every change is listed in the Changelog, and a tool rename or removal, or the removal of a response field, is announced there at least 30 days before it takes effect. Results come from live registry, WHOIS and DNS queries and can be incomplete or out of date; confirm with the registrar before you rely on them.
For client developers
If you want to call the tools from your own script or agent, start with Call from your own code: there are no API keys, and it explains where a token comes from. If you are building or debugging an MCP client, Endpoint and transport describes the requests the server accepts, and Authorization the OAuth 2.1 flow.