Whodis MCP Server

MCP Server for checking the availability of domain names using WHOIS lookups

Local serverstdio

What is the Whodis MCP server?

MCP Server for checking the availability of domain names using WHOIS lookups. That is what the whodis mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This project provides a Model Context Protocol (MCP) server specifically designed to check the availability of domain names using WHOIS lookups. It allows AI assistants or other tools to integrate domain availability checks into their workflows.

  • Domain Availability Checks — Uses the whoiser library to perform WHOIS lookups and determine if domains appear to be available or registered
  • MCP Tool Integration — Exposes a check-domain-availability tool for MCP clients (like AI assistants)
  • CLI Interface — Includes a command-line interface (whodis-mcp-server check-domain-availability ...) for direct usage and testing
  • Structured Logging — Provides detailed logging for debugging and monitoring
  • Configurable — Supports configuration via environment variables or .env files

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

  • Node.js (>=18.x): Download - Git: For version control ---

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by vinsidious; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Configuration

  • Node.js (>=18.x): Download - Git: For version control ---

Frequently asked questions

It returns a JSON object with two arrays: `available` (domains that appear unregistered) and `unavailable` (domains that appear registered). Domains where the lookup failed are omitted.