Talk to our APIs using LLMs. Connect your preferred LLM to WhoisXML API and simply chat about WHOIS, DNS, threat intelligence, and more – the LLM will perform the API calls and give you the information you need.
No need to leave the chat – keep talking to the same LLM in the same window, it’ll do all the lookup work for you.
LLMs understand what you want and convert your requests into API calls. Then, they parse JSON and return the specific information you wanted in a human-friendly format.
Tell the LLM all the data points you need to perform the specific lookups for – and it will perform them. No need to code API requests.
Write complex, multi-step queries that make LLMs send requests to multiple APIs and pivot off the data they receive. Then just hit enter – and make yourself a cup of tea while the LLM would follow your instructions, mapping entire infrastructures or attack surfaces.
LLMs can’t access real-time data natively. The MCP server allows them to retrieve up-to-date WHOIS, DNS, SSL certificate and threat intelligence data on demand to power cybersecurity investigations or SOC workflows.
With one query specifying a domain, LLMs can use the MCP server to gather subdomains and WHOIS ownership details, as well as perform reverse IP lookups and more to build an inventory of the organization’s exposed assets.
The MCP server gives LLMs access to reverse WHOIS, related domains, or historical DNS data instantly – with the ability to pivot off the results to build complete infrastructure reports.
With MCP, you can embed an LLM that understands natural language and triggers API-based lookups on demand into your tool—transforming prompts like “Show all domains registered with this email” into real investigations.
We invite cybersecurity specialists, researchers, marketers, law enforcement professionals, and product developers to request an exclusive demonstration of the WhoisXML API MCP Server, a powerful bridge between artificial intelligence tools and extensive domain, IP, and DNS intelligence infrastructure.
This session will provide a practical overview of:
Participation is currently limited to verified professionals in cybersecurity and adjacent fields.
Your hosts:
LLMs supported include the below and many more:
An MCP server is a modular system that acts as a bridge between a large language model (LLM) and APIs. MCP stands for Model Context Protocol – a protocol developed by Anthropic in 2024. MCP servers allow the LLM to delegate tasks that it cannot perform on its own to external tools via APIs. It receives structured calls (often from a model’s tool-use or function-calling capabilities), executes API requests or computations, and returns the results in a format the model can understand. This architecture enables LLMs to interact with external systems, databases, and services in a secure, controllable, and scalable manner.
In the case of WhoisXML API, our MCP server allows you to enable LLMs that support the MCP protocol to access our APIs, run API requests, and receive responses. LLMs then process the JSON or XML response and return the information you were looking for.
Currently, WhoisXML API’s MCP server works with the following APIs:
We are working on integrating other APIs with the MCP server as well.
Yes, the MCP server itself is available for free, you only need to pay for the API credits that you use. You get some free credits upon signup which should be enough to test the MCP server out.
Yes, you do – the LLMs would use the same API key you use to run API queries. The API key is the only parameter you need to configure in the MCP server. You can find yours in yours at the top of the "My products" page.
We’ve documented the process of installation in our documentation. It’s easy and wouldn’t take more than a few minutes of your time. After installation, you’ll need to configure the LLM that you’re using so that it is aware of the existence of the MCP server. This process is also detailed in the documentation.
Absolutely, you can think of the MCP server as just another way to run API calls through an LLM interface. As such, credits bought to use the MCP server are fully functional for using the APIs outside the MCP server.















