Domain & company intel for AI agents: RDAP, DNS, email deliverability, tech stack. No API keys.
Domain MCP server exists for a simple reason — assistants are far more useful when they can act on Domain directly instead of describing what you should do. Domain & company intel for AI agents: RDAP, DNS, email deliverability, tech stack. No API keys.
Domain and company intelligence for AI agents. Give an agent a domain or email address and it can vet the company, qualify the lead, or map the target — all from free public data, no API keys.
Once Domain is connected, these are the calls the assistant has available:
domain_intel — Registrar, creation/expiry dates, domain age, EPP status, nameservers, DNSSEC, abuse contactdns_lookup — A, AAAA, MX, NS, TXT, CNAME, SOA recordsemail_deliverability — MX presence, SPF/DMARC posture, free vs. disposable provider, verdicttech_stack — Web server, CMS/framework, CDN, analytics, security headers, page titlesubdomains — Subdomain discovery from Certificate Transparency logsdomain_report — One call returns a full dossier: registration + DNS + email deliverability + tech stack, combinedYou will need one environment variable: SERVER_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Domain's toolset — domain_intel, dns_lookup, email_deliverability and 3 more — is a fair guide to whether it matches your workflow. It is maintained by com.datakoot; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| domain_intel | Registrar, creation/expiry dates, domain age, EPP status, nameservers, DNSSEC, abuse contact |
| dns_lookup | A, AAAA, MX, NS, TXT, CNAME, SOA records |
| email_deliverability | MX presence, SPF/DMARC posture, free vs. disposable provider, verdict |
| tech_stack | Web server, CMS/framework, CDN, analytics, security headers, page title |
| subdomains | Subdomain discovery from Certificate Transparency logs |
| domain_report | One call returns a full dossier: registration + DNS + email deliverability + tech stack, combined |
**Claude Desktop / other clients**
```json
{
"mcpServers": {
"domain-intel": {
"command": "npx",
"args": ["mcp-remote", "https://domain.datakoot.com/mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SERVER_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.