mcp-ip2whois
Officialby ip2whois
README.md
# IP2WHOIS MCP Server
[](https://glama.ai/mcp/servers/ip2whois/mcp-ip2whois)
A Model Context Protocol (MCP) server that provides comprehensive WHOIS lookup capabilities using the **IP2WHOIS API**. This server allows AI agents to query domain registration details, including expiry dates, registrar information, and registrant data. This server also supports query on hosted domains by IP address.
## Features
- **Domain Lookup**: Retrieve detailed WHOIS data for any domain name.
- **Hosted Domains Lookup**: Retrieve hosted domains data for any IP address.
- **Comprehensive Data**: Includes domain age, nameservers, registrar info, and administrative/billing contact details.
- **FastMCP Framework**: Built using the high-performance FastMCP Python framework.
## Requirement
This MCP server requires an API key to work. You can [sign up](https://www.ip2location.io/sign-up) for a free API key and enjoy up to 500 queries per month.
The setup also use `uv`, which can be install by following [the guide](https://modelcontextprotocol.io/quickstart/server#set-up-your-environment).
## Setup
Follow the steps to use this MCP server with Claude Desktop:
1. Setup the `uv` package manager, you can once again refer to [the guide](https://modelcontextprotocol.io/quickstart/server#set-up-your-environment) to do so.
2. Make sure you have installed the Claude Desktop, if you haven't, kindly download from [here](https://claude.ai/download) for Windows and MacOS users, or follow [this guide](https://modelcontextprotocol.io/quickstart/client) for Linux user.
3. Open the `claude_desktop_config.json` in your choice of editor, if you do not having one yet, follow [this guide](https://modelcontextprotocol.io/quickstart/server#testing-your-server-with-claude-for-desktop) to create one.
4. Add the following to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"ip2whois": {
"command": "uvx",
"args": ["mcp-ip2whois"],
"env": {
"IP2WHOIS_API_KEY": "<YOUR API key HERE>"
}
}
}
}
```
5. To get your API key, just [login](https://www.ip2location.io/log-in) to your dashboard and get it from there. Replaced the `<YOUR API key HERE>` in above with your actual API key.
6. Restart the Claude Desktop after save the changes, and you should see it appear in the `Search and tools` menu.
## Usage
To query the WHOIS information, just enter your query about the domain in a chat in Claude Desktop. Some of the example query will be:
- Who is the registrar of the (domain)?
- Who is the owner of (domain)?
- What is the WHOIS for (domain)?
For instance, below is the result of the domain google.com:

To query for the hosted domains by IP address, just enter your query about the IP in a chat in Claude Desktop. Some of the example query will be:
- What domains did (IP) have?
- What are the domains in (IP)?
- What's the domain owned by (IP)?
In Claude Desktop, the model will automatically generate the output based on the result returned by IP2WHOIS MCP server.
## Environment Variable
`IP2WHOIS_API_KEY`
The IP2WHOIS API key, which allows you to query up to 500 per month for free and more details of the IP address. You can [sign up](https://www.ip2location.io/sign-up) for a free API key, or [subscribe](https://www.ip2location.io/pricing) to a plan to enjoy more benefits.
## Tools
### `get_whois`
Look up WHOIS data for a domain name.
- **Arguments**:
- `domain` (string): The domain name to look up (e.g., `google.com`).
- **Output**: Returns a JSON object containing:
- `domain_id`, `status`, `domain_age`
- `create_date`, `update_date`, `expire_date`
- `registrar` (name, url, etc.)
- `registrant` (name, organization, country)
- `nameservers`
### `get_hosted_domains`
Query for the list of hosted domain names by IP address.
- **Arguments**:
- `ip` (string): The IP address (IPv4 or IPv6) to look up.
- **Output**: Returns a JSON object containing the domains hosted on the ip address, and the total number of hosted domains found
## License
See the LICENSE file.
<!-- mcp-name: io.github.ip2whois/mcp-ip2whois -->TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one resolves IP addresses to hosted domains, the other retrieves WHOIS data for domain names. There is no functional overlap.
Naming Consistency5/5
Both tools follow the consistent verb_noun pattern (get_hosted_domains, get_whois), making the naming predictable and easy to understand.
Tool Count3/5
With only two tools, the server feels minimal for the domain of IP and domain information. While the tools cover core functionalities, the count is at the lower boundary of what's reasonable.
Completeness3/5
The tools cover hosted domains and WHOIS lookups, but common related operations like IP geolocation, domain availability checks, or reverse IP lookups are missing. The surface is functional but not comprehensive.
Maintenance
ActivityInactive
ResponsivenessNo issues