WDC MCP · Model Context Protocol
Connect AI to WHOIS, Domain, Company & Internet Intelligence
Give ChatGPT, Claude, Cursor, Gemini, VS Code, and other AI agents direct access to WhoisDataCenter intelligence — WHOIS records, historical domain data, companies, emails, phones, IPs, DNS, SSL certificates, subdomains, technologies, cybersecurity signals, and more, all from one connection.
One MCP. Billions of records. One simple AI conversation.
Ask, don’t search
Instead of searching different databases and APIs, simply ask your AI agent. It selects the right WhoisDataCenter tools, searches the data, and gives you one useful answer.
“Give me everything you know about example.com.”
“Who owns this domain?”
“Show me the WHOIS history.”
“What company operates this website?”
“Find business emails for this company.”
“Find people connected with this company.”
“Find all domains connected with this email.”
“Show me every domain using this IP.”
“Find subdomains and SSL certificates.”
“Check if this domain has security risks.”
What it looks like
A plain-English question, the tools the agent reaches for on its own, and one combined answer.
WhoisDataCenter MCP is a Model Context Protocol server that connects AI applications directly with WhoisDataCenter data. It gives AI agents structured access to domain, WHOIS, company, contact, network, DNS, technology, and cybersecurity intelligence.
Instead of building many API integrations, you connect one MCP server — your AI agent then searches whichever dataset it needs, automatically.
Beyond registration lookups
Traditional WHOIS tells you about a domain registration. WhoisDataCenter MCP goes much further — a single domain can be connected with:
Your AI agent can connect these signals to build a much bigger picture.
Every dataset, one connection
Access current and historical WHOIS information.
“Show me how the ownership of example.com changed over time.”
Start with information about a person or company and discover connected domains.
“Find domains connected with [email protected].”
“Find domains registered to Example Technologies Ltd.”
Reverse searches can help discover relationships that are difficult to find with a normal domain lookup.
Turn a domain into company information.
“Research the company behind example.com.”
Search available email intelligence connected with domains, people, and companies.
“Find available business emails for this company.”
The AI can combine email information with company and domain intelligence to provide better context.
Discover available people connected with companies and websites.
“Find people working in cybersecurity at this company.”
Search phone information connected with domains and businesses.
“What domains have been connected with this phone number?”
Give your AI access to DNS infrastructure.
“Show me the DNS infrastructure behind example.com.”
Investigate IPv4 and IPv6 infrastructure.
“Find domains hosted on the same IP as example.com.”
Research SSL certificates and certificate relationships.
“Find other domains connected with this SSL certificate.”
Discover known subdomains.
“Find all known subdomains for example.com.”
Your AI can combine subdomain information with IP, SSL, DNS, and technology data for deeper infrastructure research.
Understand what technologies a website uses.
“Which companies use WordPress and Cloudflare?”
Access newly registered domain intelligence through your AI agent.
“Find newly registered .com domains containing the word "security".”
The AI can then enrich these domains with other available WhoisDataCenter data.
Use WhoisDataCenter MCP for domain and infrastructure investigations.
“Investigate suspicious-example.com and give me a security report.”
The AI can automatically use several tools and combine the results.
Research businesses before contacting them.
“Research example.com as a possible customer.”
This can help sales and research teams understand a company before contacting it.
A domain can be the starting point for a much larger investigation. Ask “Enrich example.com” and the AI searches multiple sources, ending in one combined domain intelligence profile.
You can also start with a company. Ask for “a complete intelligence profile for Example Inc.” and the AI works outward from there — useful for far more than domain research.
Ask “Investigate example.com” and your AI agent could, in order:
You do not need to call every tool yourself — the AI agent decides which ones it needs.
Start your investigation with almost any piece of information — useful for relationship discovery and internet intelligence.
Connect WhoisDataCenter MCP with any MCP-compatible application.
A start-to-finish walkthrough for connecting the WhoisDataCenter MCP server to Claude — so you can ask, in plain English, for WHOIS records, company and contact intelligence, DNS/IP/SSL infrastructure, and cybersecurity signals, without leaving the chat.
Three things, and the whole connection takes under a minute.
WhoisDataCenter isn't (yet) in Claude's built-in directory, so you add it the same way you'd add any remote MCP server — by URL.
Open Settings in Claude, then look under Customize in the left sidebar for Connectors. (If you land on the older Settings → Connectors page, it now just points you there.)
Connectors have moved to Customize. Head there to browse, connect, and manage them.
On the Connectors page, click Add in the top-right corner.
| Connector | Type | Authorization | Status |
|---|---|---|---|
| Google Drive | Web | Individual | ✓ |
| Slack | Web | Individual | ✓ |
| Notion | Web | — | Connect |
In the Add custom connector dialog, fill in two fields:
Connect Claude to your data and tools. Learn more about connectors or get started with pre-built ones.
Click Continue. Claude reaches out to mcp.whoisdatacenter.com and moves you to authentication — the next section.
Many lookups work right away with no sign-in at all — WhoisDataCenter serves anonymous requests up to a free usage limit. If Claude shows a sign-in screen after step 2 (or once you want a higher limit or your paid plan), it accepts your regular WhoisDataCenter account (email + password, or Google).
There's no self-service "API key" page in your WhoisDataCenter account — a backup API key is only ever issued automatically by email after a paid checkout, for the rare case where you need to connect from a different network than the one you originally signed up from. You won't normally need one. If you do have one, enter it only inside the authentication screen Claude opens for this connector — never in a chat message or shared doc.
Once sign-in succeeds (if it was shown), the connector's row on the Connectors page shows a checkmark under Status, and it's ready either way.
Connecting an account makes the connector available; you still flip it on per chat (or set it to stay on by default) from the tools/connector picker in the message composer — usually a small + or tools control next to where you type. Toggle WhoisDataCenter on there.
From that point, you don't call any tool by name — just ask a normal question. Claude decides on its own which of WhoisDataCenter's WHOIS, company, DNS, IP, SSL, or cybersecurity tools to run, sometimes chaining several together for one answer.
Ask the way you'd ask a colleague — a domain, a company, an email, a phone number, or an IP are all valid starting points.
One connector, sourced from 50+ registries (ICANN, AFNIC, Nominet, DNS Belgium, and others). Claude reaches into whichever of these it needs for your question.
Current + historical WHOIS, ownership and registrar changes, domain age and status.
Start from an email, phone, name, or company and find connected domains.
Industry, size, location, related sites and infrastructure behind a domain.
Business emails and numbers linked to a domain, person, or company.
Names, titles, and social profiles connected to a company or site.
A/AAAA/MX/TXT records, nameservers, ASN, hosting, reverse-IP neighbors.
Certificate issuer/subject history and known subdomains for a domain.
CMS, web server, and other stack signals detected on a site.
Newly registered domains, blacklist and typosquatting signals.
Same server, same credentials — only the settings screen changes.
Claude Desktop: Settings → Connectors → Add custom connector, same two fields as above.
Claude Code / other MCP clients: drop this into your MCP config file:
{
"mcpServers": {
"whoisdatacenter": {
"url": "https://mcp.whoisdatacenter.com/"
}
}
}Full API reference
The capability cards above group tools by use case. This is the literal tool surface the server exposes — every tool name and parameter, for wiring up a client or debugging a call.
resolve_queryResolve a free-text value — an email address, phone number, IP address, or company name — down to the domain it's associated with.
kindenumrequireddomain · email · phone · ip · companyvaluestringrequiredthe free-text value to resolveSetup takes under a minute
https://mcp.whoisdatacenter.com/{
"mcpServers": {
"whoisdatacenter": {
"url": "https://mcp.whoisdatacenter.com/"
}
}
}Authenticate using your WhoisDataCenter credentials or API key. Your API key should always be kept private.
One MCP for internet intelligence
WhoisDataCenter MCP brings together domain registration, historical WHOIS, company, contact, DNS, IP, SSL, subdomain, technology, and cybersecurity intelligence. Connect once. Ask questions in plain English. Let your AI agent do the research.
https://mcp.whoisdatacenter.com/