How do I use whois-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@whois-mcp look up google.com" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

whois-mcp

by simplebytes-com

Overview Schema Related Servers Score Discussions

JavaScript

Hybrid

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

Option 1: Local Installation (Recommended for Claude Desktop)

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:

Repository: https://github.com/simplebytes-com/whois-parser
Author: Simple Bytes LLC
License: MIT

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:

Bundles source files with esbuild
Adds shebang for CLI execution
Copies whois_dict.json and fetch-iana-servers.js to build directory
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

domaindetails-mcp - Full-featured domain research toolkit with RDAP, WHOIS, and DNS lookup
rdap-mcp - Simple RDAP-only MCP server
whois-parser - Comprehensive WHOIS parser for 169 ccTLDs
DomainDetails.com - Full-featured domain research SaaS

Support

Issues: https://github.com/simplebytes-com/whois-mcp/issues
Website: https://domaindetails.com
Email: support@domaindetails.com

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.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of TLDs to return (default: all)

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description clearly states it returns the complete list, with no destructive or side effects implied. It lacks details on output format but is still informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with front-loaded purpose, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple listing tool with one optional parameter, the description is adequate. Could mention return type (e.g., list of strings) but not required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the description does not add new information about the limit parameter beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb and resource: 'List all supported TLDs', and contrasts with siblings: refresh_whois_servers and whois_lookup, which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage before whois_lookup by stating it lists TLDs that can be queried, but does not explicitly state when to use or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It describes the behavior (fetching from IANA, updating server list) and implies it is a safe update operation. However, it does not disclose potential side effects (e.g., clearing existing list), duration, or authentication needs, leaving some behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with high information density. The first sentence states the core action, the second explains the purpose, and the third provides usage guidance. No extraneous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters, no output schema, and a simple action, the description is mostly complete. It explains what the tool does and when to use it. However, it could mention any return value or confirmation, but lacking an output schema reduces the need.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters with 100% schema description coverage, so baseline is 4. The description does not need to add parameter details. It appropriately focuses on the tool's action without redundant parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action: 'Refresh the WHOIS server dictionary by fetching the latest TLD list from IANA.' This verb-resource pairing is specific and distinguishes it from sibling tools like list_supported_tlds and whois_lookup, which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides advice to 'Run this periodically to ensure the server list is up-to-date,' which suggests a maintenance use case. However, it lacks explicit guidance on when not to use it or alternatives. The instruction is vague and does not specify frequency or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

ParametersJSON Schema

Name	Required	Description	Default
`domain`	Yes	The domain name to look up (e.g., example.com, theo.gg, mineo.pl)
`include_raw`	No	If true, include raw WHOIS response data in the result

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; the description mentions querying authoritative WHOIS servers and supporting 1,260+ TLDs, but lacks details on rate limits, error handling, or data completeness. Some behavioral context is present but insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: first states the action, second details the output and scope. No superfluous information, well front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with two parameters and no output schema, the description covers the main functionality and supported TLDs. It could mention response format or potential delays, but overall is adequate for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are fully documented in the input schema (100% coverage). The description adds no additional meaning beyond what the schema already provides, meeting the baseline for schema-rich tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs WHOIS lookups for domain registration details, specifying the protocol and supported TLD count. It distinguishes from sibling tools (list_supported_tlds, refresh_whois_servers) implicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but does not explicitly specify when to use it over alternatives or mention exclusions. Given the sibling names, usage context is implied but not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0Jul 6, 2026
- First observedlist_supported_tlds
- First observedrefresh_whois_servers
- First observedwhois_lookup

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0

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

ActivityStale

ResponsivenessUnresponsive

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

WHOIS A
io.github.KincaidYang
Query WHOIS/RDAP information for domains, IP addresses, CIDR prefixes and ASNs. Self-hostable.
Networking & Infrastructure Security
2264
RDAP API A
io.rdapapi
Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
71
whois-mcp
ru.wwhois
WHOIS/RDAP lookup, IP geolocation and Punycode conversion. 1400+ TLDs incl. IDN. No API key.
Networking & Infrastructure Location Services
11
Domain RDAP MCP A
io.github.Lulu-The-Narwhal
Free, keyless domain registration lookup via RDAP: registered, available, registrar, expiration.
Networking & Infrastructure Open Data Search
11

Related MCP Servers

Whois MCP
Search RAG Systems
bharathvaj-ganesan
A
license
A
quality
F
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.
Updated a year ago (2025-03-15 10:21 UTC)
4
1,956
60
MIT
Domain Tools MCP Server
Web Scraping
deshabhishek007
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.
Updated a year ago (2025-06-20 18:48 UTC)
14
MIT
Lookup-Domain
Entertainment & Media
xiaobenyang-com
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.
Updated 8 months ago (2026-01-09 07:06 UTC)
1
2
Apache 2.0
whois-mcp
Entertainment & Media
xiaobenyang-com
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.
Updated 8 months ago (2026-01-09 07:06 UTC)
3
2
Apache 2.0

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/simplebytes-com/whois-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

WHOIS MCP Server

Features

Installation

Usage

Option 1: Local Installation (Recommended for Claude Desktop)

Option 2: Hosted Version

Available Tools

whois_lookup

list_supported_tlds

refresh_whois_servers

WHOIS Data

Supported TLDs

Parser Features

Technical Details

Architecture

Attribution

Development

Build Process

Updating the WHOIS Dictionary

Examples

Example 1: .com Domain (google.com)

Example 2: .gg ccTLD (theo.gg)

Example 3: .pl ccTLD (mineo.pl)

Troubleshooting

No WHOIS Server Found

Connection Timeout

Parsing Issues

License

Related Projects

Support

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

`whois_lookup`

`list_supported_tlds`

`refresh_whois_servers`