hackerdogs/whoisxmlapi-mcp repository overview

⁠

⁠Whoisxmlapi MCP Server

MCP server wrapper for WhoisXML API⁠ — local compliance stub that points to the hosted production MCP endpoint at https://mcp.whoisxmlapi.com/mcp⁠.

⁠What is Whoisxmlapi?

WhoisXML API is a commercial domain intelligence platform offering WHOIS history, DNS lookup, IP geolocation, domain reputation, subdomain discovery, reverse WHOIS, and threat intelligence feeds across billions of records. See whoisxmlapi.com⁠ for full documentation. This Docker image is a local compliance stub — the single remote_endpoint_info tool returns the official production MCP URL (https://mcp.whoisxmlapi.com/mcp) where the full WhoisXML API toolset is available. An API key from whoisxmlapi.com is required to use the production endpoint.

⁠Tools Reference

⁠Example Prompts

Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:

• "What is the production MCP endpoint URL for WhoisXML API?"
• "Get the WhoisXML API remote MCP connection details so I can configure my client."
• "Use WhoisXML API to look up WHOIS history for example.com — what endpoint should I connect to?"
• "Show me how to connect to the WhoisXML API MCP server for domain intelligence queries."
• "Return the remote endpoint info for the WhoisXML API integration."
• "What tools are available through the WhoisXML API MCP production endpoint?"

⁠Deploy

⁠Docker Compose (recommended)

docker-compose up -d

⁠Docker Run (stdio mode)

docker run -i --rm hackerdogs/whoisxmlapi-mcp:latest

⁠Docker Run (HTTP streamable mode)

docker run -d -p 8511:8511 \
  -e MCP_TRANSPORT=streamable-http \
  -e MCP_PORT=8511 \
  hackerdogs/whoisxmlapi-mcp:latest

⁠MCP Client Configuration

⁠Stdio mode (default)

Add to your Claude Desktop or Cursor MCP config:

{
  "mcpServers": {
    "whoisxmlapi-mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT", "hackerdogs/whoisxmlapi-mcp:latest"],
      "env": {
        "MCP_TRANSPORT": "stdio"
      }
    }
  }
}

⁠HTTP mode (streamable-http)

First, start the server using Docker Compose or docker run with HTTP mode (see Deploy⁠ above), then point your MCP client at the running server:

{
  "mcpServers": {
    "whoisxmlapi-mcp": {
      "url": "http://localhost:8511/mcp"
    }
  }
}

⁠Environment Variables

⁠Installing in Hackerdogs

The fastest way to get started is through Hackerdogs⁠:

1. Log in to your Hackerdogs account.
2. Go to the Tools Catalog.
3. Search for the tool by name (e.g. "nuclei", "naabu", "julius").
4. Expand the tool card and click Install — you're ready to go.

1. Vendor API key required? Add your key in the config environment variable field before clicking Install. Your key will be encrypted at rest.
2. Enable / Disable the tool anytime from the Enabled Tools page.
3. Need to update a key or parameter? Go to My Tools → toggle Show Decrypted Values → edit → Save.

⁠Build

docker build -t hackerdogs/whoisxmlapi-mcp:latest .

⁠Testing

⁠Automated tests

./test.sh

⁠Test directly with Docker

1. Start the server in HTTP mode:

docker run -d --rm --name whoisxmlapi-mcp-test -p 8511:8511 \
  -e MCP_TRANSPORT=streamable-http \
  hackerdogs/whoisxmlapi-mcp:latest

2. Initialize the MCP session:

SESSION_ID=$(curl -s -D - -X POST http://localhost:8511/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
  2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')

curl -s -X POST http://localhost:8511/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","method":"notifications/initialized"}'

3. Call a tool:

curl -s -X POST http://localhost:8511/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"run_whoisxmlapi","arguments":{"arguments":"--help"}}}'

4. Clean up:

docker stop whoisxmlapi-mcp-test

⁠Running the tool directly (bypassing MCP)

You can run the Whoisxmlapi CLI in the same container by overriding the entrypoint without starting the MCP server.

Show help:

docker run -i --rm --entrypoint whoisxmlapi hackerdogs/whoisxmlapi-mcp:latest --help