Whodis MCP Server provides a domain availability checker via the MCP protocol. It exposes a tool named check-domain-availability that takes one or more domain names and returns two lists: available (domains that appear unregistered) and unavailable (domains that are registered). This server uses the whoiser library under the hood to perform WHOIS lookups and determine availability and is designed to integrate with MCP clients such as AI assistants or automation pipelines. You can test the tool through the MCP Inspector in development mode or via the provided CLI, which makes it easy to embed domain checks into larger workflows or decision-making prompts. The server is designed to log in detail and can be configured via environment variables or a .env file for easier deployment across environments.

Prerequisites:

• Node.js (>= 18.x)
• Git
• npm (comes with Node.js)

Step-by-step installation:

1. Clone the repository git clone https://github.com/vinsidious/whodis-mcp-server.git cd whodis-mcp-server

2. Install dependencies npm install

3. (Optional) Create a .env file to customize behavior

   Example

   DEBUG=true PORT=5173

4. Run the development server npm run dev:server

5. (Optional) Run the CLI in development mode to test the tool npm run dev:cli -- check-domain-availability example.com testdomain.org

6. Build for production (if you plan to publish or run a production build) npm run build

7. Start the production server (requires MCP client integration) npm run start:server

8. Run CLI with the production build npm run start:cli -- check-domain-availability google.com

Notes and tips:

• The server relies on WHOIS lookups via the whoiser library, which may vary in reliability across TLDs and network conditions. Domains that fail to lookup are omitted from the results.
• Debug logs can be very verbose. Enable DEBUG=true to surface detailed request/response logs and MCP Inspector data during development.
• Logs are also written to ~/.mcp/data/whodis-mcp-server.*.log for easier post-mortem analysis.
• If you deploy in a container or cloud environment, ensure port 5173 (or your configured PORT) is open and that the MCP client can reach the server URL.
• The MCP tool is named check-domain-availability and expects a JSON payload with a domains array; the response contains available and unavailable arrays.
• You can customize the environment by adding additional variables as needed, such as timeouts or DNS resolution tweaks, depending on your hosting environment.