Skip to main content
Glama
mcp-ip2whois

mcp-ip2whois

Official
by ip2whois

IP2WHOIS MCP Server

mcp-ip2whois MCP server Ip2whois MCP on mcprush

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.

Related MCP server: Whodis MCP Server

Requirement

This MCP server requires an API key to work. You can sign up for a free API key and enjoy up to 500 queries per month.

The local MCP server setup also uses uv, which can be installed by following the guide.

Setup

There are two ways to use this MCP server:

  • Cloud-hosted MCP server: Connect directly to the hosted IP2WHOIS MCP server. Nothing needs to be installed locally.

  • Local MCP server: Download and run the server on your own machine with uv.

Option 1: Cloud-hosted MCP server

Use this if you want to connect directly to the hosted server.

Method A: Direct HTTP connection

Use this if your MCP client supports remote servers over HTTP. No uv, Node.js, or npx is needed.

{
  "mcpServers": {
    "ip2whois": {
      "type": "http",
      "url": "https://mcp.ip2whois.com/",
      "headers": {
        "X-API-Key": "<YOUR API key HERE>"
      }
    }
  }
}

If your client is configured from the command line, such as Claude Code, you can add the server with:

claude mcp add --transport http ip2whois https://mcp.ip2whois.com/ --header "X-API-Key: <YOUR API key HERE>"

Method B: Connection through npx

Use this if your MCP client only supports local (stdio) servers. The mcp-remote package runs locally and forwards requests to the hosted server. Node.js is required.

{
  "mcpServers": {
    "ip2whois": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.ip2whois.com/",
        "--header",
        "X-API-Key:<YOUR API key HERE>"
      ]
    }
  }
}

To get your API key, just login to your dashboard and get it from there, then replace <YOUR API key HERE> in the example above with your actual API key.

Restart the Claude Desktop after saving the changes, and you should see it appear in the Search and tools menu.

Option 2: Local MCP server

Follow the steps below to run the MCP server on your own machine:

  1. Setup the uv package manager, you can once again refer to the guide to do so.

  2. Make sure you have installed the Claude Desktop, if you haven't, kindly download from here for Windows and MacOS users, or follow this guide 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 to create one.

  4. Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "ip2whois": {
      "command": "uvx",
      "args": ["mcp-ip2whois"],
      "env": {
        "IP2WHOIS_API_KEY": "<YOUR API key HERE>"
      }
    }
  }
}
  1. To get your API key, just login to your dashboard and get it from there. Replace the <YOUR API key HERE> in the example above with your actual API key.

  2. Restart the Claude Desktop after saving 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:

The output 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 for a free API key, or subscribe 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.

Available Tools

2 tools
get_hosted_domainsA
Lookup for the list of hosted domain names by IP address.

Args:
    ip: The ip address (IPv4 or IPv6) to look up.

Returns:
    A JSON string result includes the domains hosted on the ip address, and the 
    total number of hosted domains found.

Inputs: ip (required). Returns: result

get_whoisA
Lookup WHOIS data for a domain name. Use this tool when the user asks about 
domain registration details, registrar names, expiry dates, domain ownership, 
or nameservers for a specific website (e.g., 'google.com').

Args:
    domain: The domain name to look up (e.g., 'example.com').

Returns:
    A JSON string result includes domain age, update and expiry date, assiociated nameservers, registrar and registrant information, and admin, tech and billing information.

Inputs: domain (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that allows AI agents to perform WHOIS lookups, enabling users to directly ask the AI about domain availability, ownership, registration details, and other domain information.
      4
      184 npm
      60
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to check domain name availability using WHOIS lookups.
      16 npm
      4
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      A WHOIS domain name query server based on Model Context Protocol (MCP), supporting the resolution of over 877 top-level domains and 169 country code top-level domains, and providing comprehensive domain name registration information query functions.
      3
      2
      Apache 2.0