Domain Tools MCP Server: WHOIS and DNS Health

Overview

Domain Tools MCP Server provides a lightweight Model Context Protocol (MCP) endpoint for performing domain analysis: WHOIS lookups, DNS record inspection, and DNS health checks. It wraps common domain diagnostics into an API-friendly service so other tools, agents, or models can query authoritative domain metadata and runtime DNS health information programmatically.

This server is useful for developers building automation around domain onboarding, incident response, reputation checks, or monitoring pipelines. By exposing WHOIS and DNS checks as a consistent API, you can integrate domain diagnostics into CI jobs, observability dashboards, or conversational agents that require real-time domain context.

Features

• Perform authoritative WHOIS lookups for a domain
• Query DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA, etc.)
• Run DNS health checks (resolver behavior, propagation, TTL analysis)
• Simple HTTP API compatible with MCP-style integrations
• Local development and Docker deployment examples
• Configurable timeouts and resolver lists

Installation / Configuration

Prerequisites:

• Node.js (>= 14) and npm, or Docker

Clone and install:

git clone https://github.com/deshabhishek007/domain-tools-mcp-server.git
cd domain-tools-mcp-server
npm install

Environment configuration Create a .env file or export variables. Typical settings:

PORT=3000
WHOIS_TIMEOUT_MS=10000
DNS_TIMEOUT_MS=5000
DNS_RESOLVERS=8.8.8.8,1.1.1.1
LOG_LEVEL=info

Start locally:

npm run start
# or for development with live reload (if available)
npm run dev

Run with Docker:

# Example Dockerfile (if not included in repo)
FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
ENV PORT=3000
EXPOSE 3000
CMD ["node", "index.js"]

Build and run:

docker build -t domain-tools-mcp-server .
docker run -p 3000:3000 -e PORT=3000 domain-tools-mcp-server

Available Resources

The server exposes HTTP endpoints that are designed to be used by other services or MCP-compatible clients. Typical endpoints and parameters:

Example: WHOIS request

curl "http://localhost:3000/whois?domain=example.com"

Example JSON response (illustrative)

{
  "domain": "example.com",
  "registrar": "Example Registrar, Inc.",
  "created": "1995-08-13T00:00:00Z",
  "expires": "2026-08-12T23:59:59Z",
  "status": ["clientTransferProhibited"],
  "raw": "Raw WHOIS text..."
}

Example: DNS record query

curl "http://localhost:3000/dns?domain=example.com&type=MX"

Example JSON response (illustrative)

{
  "domain": "example.com",
  "type": "MX",
  "records": [
    {"preference": 10, "exchange": "mx1.example.net."},
    {"preference": 20, "exchange": "mx2.example.net."}
  ]
}

Example: DNS health check

curl "http://localhost:3000/dns/health?domain=example.com"

Example JSON response (illustrative)

{
  "domain": "example.com",
  "resolvers_tested": ["8.8.8.8","1.1.1.1"],
  "consistency": true,
  "problems": [],
  "details": {
    "ttl_variance": "low",
    "soa_serial": "2026041501"
  }
}

Use Cases

• Automated onboarding: Verify domain WHOIS details and DNS records as part of a provisioning pipeline. Example: run /whois and /dns checks before accepting a customer domain for hosting.
• Monitoring and alerting: Schedule periodic /dns/health checks to detect propagation issues or inconsistent responses across resolvers and trigger alerts if inconsistency is detected.
• Incident response: Quickly fetch authoritative WHOIS data and recent DNS record state to investigate domain hijacking, expired registrations, or misconfigured DNS entries.
• Chatbots and ML agents: Provide condensed domain context to models or assistants. The MCP-style API lets agents request domain metadata in real time and make informed recommendations or actions.
• CI/CD validations: Validate that newly published DNS records (TXT, CNAME) have propagated and meet expected TTLs before completing a release.

Notes and Best Practices

• WHOIS data availability and format vary by TLD and registrar; treat raw WHOIS text as authoritative but parse carefully.
• Rate limits: If the server will perform large numbers of lookups, consider caching results and respecting registrar and resolver rate limits.
• Security: Avoid exposing WHOIS/diagnostic tools to the public if they will be used for internal diagnostics; secure with API keys or network controls as needed.
• Customization: Configure resolver lists to target regional DNS servers or internal resolvers for accurate environment-specific health checks.

For source code and issue tracking, see the project repository on GitHub: https://github.com/deshabhishek007/domain-tools-mcp-server