The Domainyze MCP server lets an AI assistant work with the domains you monitor. Ask it "which of my portfolio names expire this quarter?", "what stage is example.com in?" or "add these ten names to my watchlist", and it answers from your account instead of guessing.
MCP (Model Context Protocol) is the open standard assistants such as Claude, Cursor and VS Code use to talk to outside services. You connect once, approve what the assistant may do, and it calls Domainyze on your behalf.
Who can use it
The MCP server is included on the Pro and Business plans. On the Free plan the sign-in page explains this and offers only Cancel. See understanding plans and limits.
The server address
https://domainyze.com/mcp
That is the only thing most assistants need. They discover the sign-in flow from it automatically; there is no key to copy.
How to connect
The menu names below change between versions of each app, so look for the nearest equivalent.
Claude (claude.ai or the desktop app)
- Open Settings → Connectors and choose Add custom connector.
- Name it
Domainyzeand paste the server address. - Choose Connect. A Domainyze page opens; sign in if asked, then approve.
Claude Code
claude mcp add --transport http domainyze https://domainyze.com/mcp
Then run /mcp inside Claude Code, pick domainyze and choose Authenticate. Your browser opens the Domainyze approval page.
Cursor
Add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"domainyze": { "url": "https://domainyze.com/mcp" }
}
}
Cursor shows a Login or Needs authentication button next to the server; choose it to open the approval page.
VS Code
Add the server to .vscode/mcp.json:
{
"servers": {
"domainyze": { "type": "http", "url": "https://domainyze.com/mcp" }
}
}
Start the server from the file or the MCP view; VS Code opens the approval page.
Other clients
Any client that supports remote MCP servers over HTTP with OAuth sign-in will work with the address alone. If your client can only send a fixed header and you are on the Business plan, you can instead create a personal access token and send it as Authorization: Bearer <token>.
The approval page
Before anything is shared, Domainyze shows you:
- The app's name, as the assistant registered it.
- What it is asking to do, one line per permission, such as
domains:read: "Read your domains, their status and DNS." - Where you will be sent back, so you can spot an app that is not the one you started from.
Choose Authorize to connect or Cancel to refuse. You can approve fewer permissions only by refusing and reconnecting from a client that asks for less, so it is worth checking the list.
What the assistant can do
| Tool | What it does | Needs |
|---|---|---|
whoami |
Your plan, domain allowance and lookups left today | any |
list_domains |
A page of your watchlist or portfolio, with filters | domains:read |
get_domain |
One domain in full: settings, stage, drop forecast, recent checks | domains:read |
get_dns_zone |
The DNS records and email-authentication posture of a portfolio domain | domains:read |
list_groups |
Your domain groups | domains:read |
list_alerts |
Your alert history, newest first | alerts:read |
scan_domain |
Read a name you do not monitor, once, from its registry | scan |
check_availability, whois_lookup, check_expiry, domain_age, check_ssl, dns_lookup, dns_propagation, email_deliverability, typosquat_check, name_ideas, bulk_availability, punycode_convert |
The free domain tools, for any name, spending lookups | scan |
add_domains |
Start monitoring up to 100 names in a lane | domains:write |
check_domain |
Queue a fresh check of a domain you monitor | domains:write |
An assistant only sees the tools its permissions allow.
What it cannot do
On purpose, an assistant can only read and add. It cannot change a domain's settings, pause, move, regroup or remove anything, and it never sees billing, alert destinations, tokens or other accounts. Those stay in the app (and, on Business, the REST API).
The reason is safety. Some of what Domainyze returns is written by other people: WHOIS text, DNS TXT records, registrar remarks. Text like that can contain instructions aimed at an AI. Keeping the assistant's tools to reads and additions means that even a misled assistant cannot delete or reconfigure your monitoring.
Staying connected
The assistant's access refreshes itself while you use it. If it goes unused for 30 days, it has to sign in again. Each scan or domain tool it runs spends lookups from your plan's monthly budget, shared with the REST API (Pro 300 a month, Business 1,500); you can watch it under Settings → Subscription. Details are in API and MCP limits and errors.
Disconnecting
Go to Settings → API & MCP → Connected apps and choose Disconnect next to the app, or Disconnect all. The app loses access immediately. Deleting your account disconnects everything.
If you move to the Free plan, a connected app stays listed but every request it makes is refused until you upgrade again; you do not need to reconnect.