io.github.Bishop81/domainintel-mcp
Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@domainintel/mcpclaude mcp add domainintel-mcp -- npx -y @domainintel/mcp@1.0.2
{
"mcpServers": {
"domainintel-mcp": {
"command": "npx",
"args": [
"-y",
"@domainintel/mcp@1.0.2"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
@domainintel/mcp
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.
Tools
| 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.
Requirements
- Node.js 18 or newer
Install
Claude Code
claude mcp add domainintel -- npx -y @domainintel/mcp
Claude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"domainintel": {
"command": "npx",
"args": ["-y", "@domainintel/mcp"]
}
}
}
Any other MCP client
The server speaks MCP over stdio:
npx -y @domainintel/mcp
Example prompts
- "Run a full domain report on stripe.com"
- "What are the MX records for github.com, and does it have DMARC?"
- "Is the SSL certificate for example.org close to expiring?"
Development
Run from source (no build needed):
git clone <repo> && cd domainintel.app
npm install
npm run mcp # node mcp/server.mjs
Building & publishing
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
License
MIT
Frequently asked questions
What is io.github.Bishop81/domainintel-mcp?
Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.
How do I install io.github.Bishop81/domainintel-mcp?
It runs on your machine. In Claude Code: claude mcp add domainintel-mcp -- npx -y @domainintel/mcp@1.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.Bishop81/domainintel-mcp need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.Bishop81/domainintel-mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.Bishop81/domainintel-mcp?
It is published by Bishop81. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.