mcpbeat Sign in

who.is MCP Server

answering

who.is is answering right now. Last checked 5 min ago.

Parsed WHOIS, RDAP, DNS, certificates, nameservers and domain history for any domain.

Uptime history 11 days of history · worst day 99%
11 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
520 ms
Response time
average over 24h
authentication required
Access
streamable-http

who.is missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add whois --transport http https://api.who.is/v1/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.who.is/v1/mcp
~/.codex/config.toml
[mcp_servers.whois]
url = "https://api.who.is/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "whois": {
      "url": "https://api.who.is/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "whois": {
      "type": "http",
      "url": "https://api.who.is/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://api.who.is/v1/mcp streamable-http needs auth 467 ms 5 min ago

Alternatives to who.is

same job, measured the same way
MCP Whois Domain Lookup
by mambabuilt

Registrar, created and expiry dates, domain age, and nameservers per domain, from RDAP and WHOIS

local only
DomainKit
by olsols4

DNS records, SSL certificate, WHOIS/RDAP and website tech scan for any domain

answering
Hivex: .si names, DNS and WHOIS
by hivex

Find and check free .si names (600,000+ indexed), and look up DNS and WHOIS for any domain.

4 tools answering
Whois MCP
by mrfentmen

RDAP whois records for domains and IPs.

61 installs/wk local only
WHOIS & Domain Availability (RDAP)
by winters-works-co

Domain WHOIS via official RDAP: registrar, expiry dates, nameservers, availability. Winters Works.

answering
DNS
by ofershap

MCP server for DNS lookups, reverse DNS, WHOIS, and domain checks — zero auth, zero config

53 installs/wk local only
Domain Checker MCP
by wearebravelabs

Fast domain availability checker. DNS + RDAP/WHOIS verification.

37 installs/wk local only
DomainAge
by workers-mike-tusa-domainage

Domain age and RDAP lookup: registration date, age, expiry, registrar, status and nameservers.

1 tools answering

who.is — questions

Answers built from our own checks of this server.

Why is there no tool list for who.is?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is who.is working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 520 ms. The bar chart above shows every period we have measured.
How do I connect who.is?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does who.is need an API key?
Yes. Every time we knock, who.is answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is who.is?
It answers our handshake in 520 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.