Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.
An MCP server that gives AI agents live domain intelligence: WHOIS, DNS, SSL/TLS, HTTP security headers, reputation, and subdomain discovery for any domain. It is the same analysis engine that powers DomainIntel.app.
| Tool | Returns |
|---|---|
whois_lookup | Registrar, creation/expiry/updated dates, registrant country, privacy status, nameservers |
dns_records | A, AAAA, MX, TXT, NS, CNAME, CAA records + SPF/DMARC presence + misconfiguration warnings |
ssl_certificate | Validity, issuer, expiration, days remaining, protocol, warnings |
security_headers | HSTS, CSP, X-Frame-Options and others, scored with recommendations |
domain_reputation | DNSBL / Spamhaus blocklist checks and a reputation score |
subdomain_discovery | Subdomains via Certificate Transparency logs and common-prefix probing |
full_domain_report | Every analyzer at once plus an overall A+ to F security score |
analyze_email_headers | Parses a raw email header block: SPF/DKIM/DMARC results, the Received delivery path with timing, key envelope fields, and a From-vs-Return-Path spoofing flag |
Every tool except analyze_email_headers takes a single domain argument; protocol, www., and paths are stripped automatically. analyze_email_headers takes a headers string (a pasted raw header block) instead.
claude mcp add domainintel -- npx -y @domainintel/mcp
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"domainintel": {
"command": "npx",
"args": ["-y", "@domainintel/mcp"]
}
}
}
The server speaks MCP over stdio:
npx -y @domainintel/mcp
Run from source (no build needed):
git clone <repo> && cd domainintel.app
npm install
npm run mcp # node mcp/server.mjs
The published package is a single self-contained bundle (the analyzers and all JS dependencies are bundled with esbuild; Node built-ins resolve at runtime).
npm run build:mcp # from repo root -> mcp/dist/server.mjs
cd mcp && npm publish # prepublishOnly rebuilds the bundle
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @domainintel/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-bishop81-domainintel-mcp": {
"command": "npx",
"args": [
"-y",
"@domainintel/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@domainintel/mcpnpmio.github.Bishop81/domainintel-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.