Domain Lab

What the Domain Lab MCP server does

The Domain Lab MCP server gives AI assistants access to domain monitoring data from a Domain Lab account. It covers expiration dates, DNS records, SSL certificates, and email security settings such as SPF, DKIM, and DMARC. The service can explain detected changes rather than only returning raw records, making it useful for reviewing what changed on a domain and when.

It can inspect domains across registrars through the connected Domain Lab account. It also supports public checks for any domain, whether or not that domain is monitored in the account. These checks include domain status, DNS results, propagation, SSL details, lookalike-domain discovery, and an estimate of when an expired domain could become available.

How it works

The Domain Lab MCP server is hosted at https://mcp.domainlab.app/mcp. It uses OAuth 2.1 with PKCE for sign-in and connection approval. After an assistant connects, requests are made against the user’s Domain Lab account and are subject to the limits of that account’s plan.

The service reads only the data needed for each requested tool and does not access chat history. Account-connected operations can be restricted by using a read-only connection. Destructive domain removal requires confirmation, while other account-changing operations are marked as actions that should be requested carefully.

Setup and configuration

No local installation or environment variables are required. Add the hosted MCP URL in a supported client, then sign in to Domain Lab and approve access. Claude, ChatGPT, Claude Code, VS Code with GitHub Copilot, Cursor, and Gemini CLI are documented connection options; the setup guide also covers Windsurf.

For Claude Code, the connection uses the HTTP transport with the domainlab name. VS Code stores the endpoint in .vscode/mcp.json, while Cursor stores it in ~/.cursor/mcp.json. Gemini CLI uses its MCP add command with HTTP transport. ChatGPT requires Developer mode and OAuth authentication in its connector settings.

Tools and capabilities

Account and monitoring tools include:

• Reading overviews, digests, domain lists, domain details, history, events, alerts, AI reviews, notification rules, registrar connections, and inbox status.
• Explaining changes and listing available event types.
• Adding, updating, removing, and rescanning domains.
• Requesting AI reviews, changing domain alerts, syncing registrar data, and marking inbox items read.

Public inspection tools can check domain status, email authentication, DNS, DNS propagation, and SSL. They can also find lookalike domains and estimate a release date for an expiring domain.

Limitations and notes

The Domain Lab MCP server depends on an active Domain Lab account for account-specific information. Connected assistants see only that account’s data and inherit its plan limits. Public domain checks do not require the domain to be monitored, but they expose only public information.

Operations that modify monitoring or account data are distinct from read tools and may require confirmation. Domain removal is specifically destructive. Disconnecting an assistant is handled from Domain Lab preferences, where the connection can be revoked.