Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.
If you already use Domainintel, the domainintel mcp server is the piece that lets your assistant work with it directly. Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
whois_lookup — Registrar, creation/expiry/updated dates, registrant country, privacy status, nameserversdns_records — A, AAAA, MX, TXT, NS, CNAME, CAA records + SPF/DMARC presence + misconfiguration warningsssl_certificate — Validity, issuer, expiration, days remaining, protocol, warningssecurity_headers — HSTS, CSP, X-Frame-Options and others, scored with recommendationsdomain_reputation — DNSBL / Spamhaus blocklist checks and a reputation scoresubdomain_discovery — Subdomains via Certificate Transparency logs and common-prefix probingfull_domain_report — Every analyzer at once plus an overall A+ to F security scoreanalyze_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@domainintel/mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Domainintel's toolset — whois_lookup, dns_records, ssl_certificate and 5 more — is a fair guide to whether it matches your workflow. It is maintained by Bishop81; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| 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 |
{
"mcpServers": {
"domainintel": {
"command": "npx",
"args": ["-y", "@domainintel/mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.