
Model Context Protocol (MCP) Server
The Model Context Protocol (MCP) Server bridges AI assistants with external data sources, APIs, and services, enabling streamlined integration of complex workfl...
Integrate instant WHOIS, IP, and ASN lookups into your AI-powered workflow with the Whois MCP Server, designed for seamless development and security research.
The Whois MCP (Model Context Protocol) Server acts as a bridge between AI assistants and the WHOIS database, enabling seamless domain information lookups within development environments. Designed for integration with tools like Claude Desktop, Cursor, and Windsurf, it empowers AI agents to fetch domain registration data, ownership details, registrar information, and domain status without leaving the IDE or workflow. This eliminates the need to manually search for domain data in a browser, simplifying tasks such as checking domain availability, validating ownership, or gathering technical contacts. By connecting AI-powered agents directly to the WHOIS lookup process, the Whois MCP Server streamlines workflows for developers, security researchers, and anyone needing domain intelligence as part of their automated or agentic processes.
npx -y @bharathvaj/whois-mcp@latest
Cursor Settings
> MCP
+ Add New MCP Server
Whois Lookup
(or any name)command
npx -y @bharathvaj/whois-mcp@latest
.cursor/mcp.json
to your project:{
"mcpServers": {
"whois": {
"command": "npx",
"args": [
"-y",
"@bharathvaj/whois-mcp@latest"
]
}
}
}
Using MCP in FlowHunt
To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:
Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:
{
"whois": {
"transport": "streamable_http",
"url": "https://yourmcpserver.example/pathtothemcp/url"
}
}
Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “whois” to the actual name of your MCP server and replace the URL with your own MCP server URL.
Section | Availability | Details/Notes |
---|---|---|
Overview | ✅ | Provided in README |
List of Prompts | ⛔ | No prompt templates documented |
List of Resources | ⛔ | No explicit resources documented |
List of Tools | ✅ | 4 tools: whois_domain, whois_tld, whois_ip, whois_as |
Securing API Keys | ⛔ | No mention of API keys or env variables |
Sampling Support (less important in evaluation) | ⛔ | Not mentioned |
The Whois MCP server is focused and functional for its domain-lookup purpose, with clear tool definitions and integration instructions for Cursor. However, it lacks advanced MCP concepts like resources, prompt templates, and configuration for securing API keys. Its setup is easy for supported environments, but documentation for platforms beyond Cursor is missing.
Rating: 5/10 – Good for its specific use case, but limited in extensibility and documentation breadth.
Has a LICENSE | ✅ (MIT) |
---|---|
Has at least one tool | ✅ |
Number of Forks | 11 |
Number of Stars | 25 |
It connects AI assistants to the WHOIS database for instant domain, IP, and ASN lookups, providing critical registration and ownership data directly in your workflow.
It exposes four tools: whois_domain (domain lookup), whois_tld (TLD info), whois_ip (IP ownership), and whois_as (ASN lookup).
It supports domain availability checks, security and compliance audits, network infrastructure analysis, automated domain monitoring, and technical support operations—all within your development or agentic workflows.
No API keys or environment variables are required; the server is ready to use out-of-the-box.
Add the MCP component to your flow, open its configuration, and enter your MCP server details using the JSON format provided. This allows your AI agent to access the Whois tools seamlessly.
Empower your AI agents with domain, IP, and ASN intelligence directly in your development environment. Set up the Whois MCP Server to automate research, audits, and monitoring.
The Model Context Protocol (MCP) Server bridges AI assistants with external data sources, APIs, and services, enabling streamlined integration of complex workfl...
The ModelContextProtocol (MCP) Server acts as a bridge between AI agents and external data sources, APIs, and services, enabling FlowHunt users to build context...
The Discord MCP Server bridges AI assistants with Discord, enabling automated server management, message automation, and integration with external APIs via the ...