Skip to main content
Glama

WHOIS MCP Server

A Model Context Protocol (MCP) server that provides comprehensive WHOIS domain lookup using the proper WHOIS protocol (TCP port 43). Queries authoritative WHOIS servers directly with support for 877+ TLDs and parsing for 169 country-code TLDs.

Features

  • Native WHOIS Protocol: Direct TCP port 43 connections to authoritative WHOIS servers

  • 877+ TLDs Supported: Comprehensive dictionary of WHOIS servers for all major TLDs

  • 169 ccTLD Parsers: Format-specific parsing for country-code TLDs (.gg, .pl, .jp, .kr, .ru, .de, .it, etc.)

  • Auto-Update: Refresh WHOIS server dictionary from IANA with built-in tool

  • Comprehensive Parsing: Extracts registrar, dates, nameservers, status, DNSSEC, contacts

  • Lightweight: Single-file executable, minimal dependencies

  • Easy Integration: Works with Claude Desktop and any MCP-compatible client

Related MCP server: Domain Tools MCP Server

Installation

npm install whois-mcp

Or use directly with npx:

npx whois-mcp

Usage

Add to your Claude Desktop configuration file:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "whois": {
      "command": "npx",
      "args": ["-y", "whois-mcp"]
    }
  }
}

Restart Claude Desktop, and you'll see the WHOIS tools in the 🔌 menu.

Option 2: Hosted Version

This server is also available as a hosted service at mcp.domaindetails.com for HTTP-based integrations.

Available Tools

whois_lookup

Look up domain registration information using the proper WHOIS protocol (port 43).

Parameters:

  • domain (string, required): Domain name to look up (e.g., google.com, theo.gg, mineo.pl)

  • include_raw (boolean, optional): Include raw WHOIS response data (default: false)

Example Request:

{
  "domain": "theo.gg",
  "include_raw": false
}

Example Response:

{
  "domain": "theo.gg",
  "found": true,
  "method": "whois",
  "server": "whois.gg",
  "timestamp": "2025-10-30T11:11:32.936Z",
  "registrar": "NameCheap, Inc (https://www.namecheap.com)",
  "registrant": "Redacted for privacy",
  "creationDate": "2021-01-14T00:00:00Z",
  "expirationDate": "2026-01-14T00:00:00Z",
  "nameservers": [
    "dns1.registrar-servers.com",
    "dns2.registrar-servers.com"
  ],
  "status": [
    "Active",
    "Transfer Prohibited by Registrar"
  ],
  "parsed": {
    "domainName": "theo.gg",
    "registrar": "NameCheap, Inc (https://www.namecheap.com)",
    "creationDate": "2021-01-14T00:00:00Z",
    "expirationDate": "2026-01-14T00:00:00Z",
    "nameservers": ["dns1.registrar-servers.com", "dns2.registrar-servers.com"],
    "registrant": "Redacted for privacy",
    "status": ["Active", "Transfer Prohibited by Registrar"],
    "dnssec": null,
    "lastModified": null
  }
}

list_supported_tlds

List all TLDs that have WHOIS servers available for querying.

Parameters:

  • limit (number, optional): Maximum number of TLDs to return (default: all)

Example Response:

{
  "totalCount": 877,
  "returnedCount": 10,
  "tlds": [
    "aaa",
    "aarp",
    "abarth",
    "abb",
    "abbott",
    "abbvie",
    "abc",
    "able",
    "abogado",
    "abudhabi"
  ],
  "timestamp": "2025-10-30T11:11:32.936Z"
}

refresh_whois_servers

Refresh the WHOIS server dictionary by fetching the latest TLD list from IANA. Run this periodically to ensure the server list is up-to-date with new TLDs.

Example Response:

{
  "success": true,
  "message": "WHOIS server dictionary refreshed successfully",
  "previousCount": 877,
  "currentCount": 880,
  "added": 3,
  "timestamp": "2025-10-30T11:11:32.936Z",
  "output": "Sync complete! Updated whois_dict.json"
}

WHOIS Data

The server queries authoritative WHOIS servers via TCP port 43 and parses responses to extract:

  • Domain Name: Canonical domain name

  • Registrar: Domain registrar/registry information

  • Registration Dates: Creation, expiration, and last modified dates

  • Registrant: Domain owner information (when available, may be redacted for privacy)

  • Admin Contact: Administrative contact (when available)

  • Tech Contact: Technical contact (when available)

  • Nameservers: DNS nameservers for the domain

  • Status: Domain status codes (active, transfer prohibited, etc.)

  • DNSSEC: DNSSEC signing status

Supported TLDs

The server includes a comprehensive dictionary (whois_dict.json) with WHOIS servers for:

  • Generic TLDs: .com, .net, .org, .info, .biz, etc.

  • Country-code TLDs: 169 ccTLDs with format-specific parsers (.gg, .pl, .jp, .kr, .ru, .de, .it, .fr, .uk, .au, .nz, .ca, etc.)

  • New gTLDs: .app, .dev, .ai, .io, .me, .ly, and hundreds more

Parser Features

The included WHOIS parser supports diverse response formats:

  • Standard formats: Colon-separated key-value pairs

  • .gg/.je style: Natural language dates ("30th April 2003")

  • .jp style: Square bracket format [Domain Name] GOOGLE.JP

  • .kr style: Dotted dates 2007. 03. 02.

  • .ru style: Cyrillic fields with IP addresses

  • Multi-line sections: Status blocks, nameserver lists, contact blocks

Technical Details

Architecture

  • Protocol: Native WHOIS (TCP port 43) via Node.js net module

  • Parser: Based on whois-parser with 169 ccTLD parsers

  • Dictionary: whois_dict.json with 877+ WHOIS server mappings

  • Update Script: fetch-iana-servers.js syncs latest TLDs from IANA

  • Build: Single-file executable via esbuild

Attribution

This MCP server uses the comprehensive WHOIS parser from:

The parser includes support for 169 country-code TLDs with format-specific parsing logic.

Development

# Clone repository
git clone https://github.com/simplebytes-com/whois-mcp.git
cd whois-mcp

# Install dependencies
npm install

# Build
npm run build

# Test locally
node build/index.js

# Test with specific domains
node test-simple.js

Build Process

The build script:

  1. Bundles source files with esbuild

  2. Adds shebang for CLI execution

  3. Copies whois_dict.json and fetch-iana-servers.js to build directory

  4. Makes the executable file

Updating the WHOIS Dictionary

The WHOIS server dictionary can be updated from IANA:

cd src
node fetch-iana-servers.js

This fetches the latest TLD list from https://data.iana.org/TLD/tlds-alpha-by-domain.txt and updates whois_dict.json with current WHOIS servers.

Examples

Example 1: .com Domain (google.com)

{
  "domain": "google.com",
  "found": true,
  "server": "whois.verisign-grs.com",
  "registrar": "MarkMonitor Inc.",
  "creationDate": "1997-09-15T04:00:00Z",
  "expirationDate": "2028-09-14T04:00:00Z",
  "nameservers": ["NS1.GOOGLE.COM", "NS2.GOOGLE.COM", "NS3.GOOGLE.COM", "NS4.GOOGLE.COM"],
  "status": ["clientDeleteProhibited", "clientTransferProhibited", "clientUpdateProhibited"],
  "dnssec": "unsigned"
}

Example 2: .gg ccTLD (theo.gg)

{
  "domain": "theo.gg",
  "found": true,
  "server": "whois.gg",
  "registrar": "NameCheap, Inc",
  "registrant": "Redacted for privacy",
  "creationDate": "2021-01-14T00:00:00Z",
  "expirationDate": "2026-01-14T00:00:00Z",
  "nameservers": ["dns1.registrar-servers.com", "dns2.registrar-servers.com"],
  "status": ["Active", "Transfer Prohibited by Registrar"]
}

Example 3: .pl ccTLD (mineo.pl)

{
  "domain": "mineo.pl",
  "found": true,
  "server": "whois.dns.pl",
  "registrar": "Dynadot LLC",
  "creationDate": "2021.02.18 23:49:54",
  "expirationDate": "2027.02.18 23:49:54",
  "nameservers": ["josephine.ns.cloudflare.com", "kenneth.ns.cloudflare.com"],
  "dnssec": "Unsigned",
  "lastModified": "2024.09.03 13:16:45"
}

Troubleshooting

No WHOIS Server Found

If you get "No WHOIS server found for TLD", try refreshing the dictionary:

Use the refresh_whois_servers tool to update from IANA

Connection Timeout

Some WHOIS servers have rate limiting. Wait a few seconds and retry. The default timeout is 30 seconds.

Parsing Issues

The parser supports 169 ccTLDs, but some registries use unique formats. The raw WHOIS data is always available with include_raw: true.

License

MIT

Support

Available Tools

3 tools
list_supported_tldsA

List all supported TLDs (Top-Level Domains) that have WHOIS servers available. Returns the complete list of TLDs that can be queried.

Inputs: limit.

refresh_whois_serversA

Refresh the WHOIS server dictionary by fetching the latest TLD list from IANA. This updates the list of available WHOIS servers for domain lookups. Run this periodically to ensure the server list is up-to-date.

Inputs: no named parameters.

whois_lookupA

Look up domain information using WHOIS protocol (port 43). Queries authoritative WHOIS servers for domain registration details including registrar, registrant, dates, nameservers, and status. Supports 1,260+ TLDs.

Inputs: domain (required), include_raw.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing supported TLDs, refreshing the server list, and performing WHOIS lookups. There is no functional overlap, so agents can easily select the correct tool.

    Naming Consistency4/5

    All tool names use snake_case with a verb-noun structure (list_supported_tlds, refresh_whois_servers). whois_lookup deviates slightly by placing the verb at the end, but the pattern is still clear and consistent overall.

    Tool Count5/5

    Three tools is well-scoped for a WHOIS lookup service. Each tool serves an essential function with no redundancy or bloat, striking an appropriate balance for the domain.

    Completeness5/5

    The tool set covers all necessary operations: querying supported TLDs, updating the server list, and performing lookups. No obvious gaps exist for the core functionality of a WHOIS lookup service.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    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 provides comprehensive domain analysis capabilities including WHOIS lookups, DNS record queries, and DNS health checking.
      14
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides comprehensive domain name research tools, including RDAP, WHOIS, and DNS query functionality.
      1
      2
      Apache 2.0
    • 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