WhoisJSON

io.github.WhoisjsonPublished by GitHub account Whoisjsonv1.0.3Updated Oct 24, 2026

WHOIS, DNS, SSL, and domain availability lookups for AI assistants

VerifiedSTDIODesktop onlyWeb Search & Scraping Security & Monitoring

Server details

Identifier: io.github.Whoisjson/mcp-server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account Whoisjson for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Whoisjson%2Fmcp-server.svg)](https://sourceweft.com/mcp/io.github.Whoisjson%2Fmcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that gives an AI assistant WHOIS, DNS, SSL certificate and domain availability lookups through the WhoisJSON API.

What you can do: Look up WHOIS registration data for a domain, including registrar, dates, contacts and nameservers
Retrieve all DNS records for a domain (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, DMARC and others)
Inspect SSL/TLS certificate details and validity for a domain
Check whether a domain is available for registration
When to use it: Useful when you want an assistant to investigate a domain during research, due diligence, troubleshooting or site setup: who owns it, how its DNS is configured, whether its certificate is valid, or whether a name is still free.
Requirements: Runs locally as a stdio process via npx or a global npm install; needs Node.js 18 or newer and a WhoisJSON API key supplied in the WHOISJSON_API_KEY environment variable, obtained from the provider's dashboard. Network access to the WhoisJSON API is required.

Before you install

Requires a WhoisJSON API key stored in the WHOISJSON_API_KEY environment variable; the key is sent to the provider's API, and lookups of the domains you query go to that third party. Usage may be subject to the provider's plan limits or billing. The tools are read-only lookups.

Installation

In SourceWeft

Open WhoisJSON in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@whoisjson/mcp-server

MCP (Model Context Protocol) server for the WhoisJSON API. Exposes WHOIS, DNS, SSL, and domain availability lookups as tools for AI assistants.

Tools

Tool	Description
`whois_lookup`	WHOIS registration data for a domain (registrar, dates, contacts, nameservers…)
`dns_lookup`	All DNS records for a domain (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, DMARC…)
`ssl_check`	SSL/TLS certificate details and validity for a domain
`domain_availability`	Check if a domain is available for registration

Prerequisites

Sign up at whoisjson.com and copy your API key from the dashboard.
Node.js ≥ 18.

Installation

bash

npm install -g @whoisjson/mcp-server# or run directly with npx (no install needed):npx @whoisjson/mcp-server

npm install -g @whoisjson/mcp-server# or run directly with npx (no install needed):npx @whoisjson/mcp-server

Configuration

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or
%APPDATA%\Claude\claude_desktop_config.json (Windows):

json

{  "mcpServers": {    "whoisjson": {      "command": "npx",      "args": ["-y", "@whoisjson/mcp-server"],      "env": {        "WHOISJSON_API_KEY": "your_api_key_here"      }    }  }}

{  "mcpServers": {    "whoisjson": {      "command": "npx",      "args": ["-y", "@whoisjson/mcp-server"],      "env": {        "WHOISJSON_API_KEY": "your_api_key_here"      }    }  }}

Cursor

Edit ~/.cursor/mcp.json:

json

{  "mcpServers": {    "whoisjson": {      "command": "npx",      "args": ["-y", "@whoisjson/mcp-server"],      "env": {        "WHOISJSON_API_KEY": "your_api_key_here"      }    }  }}

{  "mcpServers": {    "whoisjson": {      "command": "npx",      "args": ["-y", "@whoisjson/mcp-server"],      "env": {        "WHOISJSON_API_KEY": "your_api_key_here"      }    }  }}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

json

{  "mcpServers": {    "whoisjson": {      "command": "npx",      "args": ["-y", "@whoisjson/mcp-server"],      "env": {        "WHOISJSON_API_KEY": "your_api_key_here"      }    }  }}

{  "mcpServers": {    "whoisjson": {      "command": "npx",      "args": ["-y", "@whoisjson/mcp-server"],      "env": {        "WHOISJSON_API_KEY": "your_api_key_here"      }    }  }}

Running locally (development)

Publishing

API reference

Full API documentation: whoisjson.com/documentation

Source: README.md at commit 17d0cc5

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.3LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.