domain-security-mcp-server
Related Servers
Alternatives to domain-security-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to perform passive security scans on domains, checking email spoofing (DMARC/SPF/DKIM), TLS weaknesses, security headers, exposed files, and subdomain-takeover risk without needing an API key.789 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to check a domain's email authentication and health across SPF, DKIM, DMARC, BIMI, MX, MTA-STS, and TLS-RPT, returning a score and recommended fixes.MIT
- AlicenseAqualityBmaintenanceDomain security reconnaissance for AI agents — 13 tools (DNS+DNSSEC, SSL/TLS, HTTP security headers, SPF/DKIM/DMARC email auth, port scan, ASN, RDAP/WHOIS) plus a one-shot security_scan returning a 0–100 Health Score (A–F). Free, no API key.33626 npm1MIT
- AlicenseAqualityAmaintenanceEnables auditing any domain's email deliverability and DNS health, including SPF, DKIM, DMARC, MX, mail provider, DNS blacklist status, catch-all, domain age, and a deliverability score.169 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to run domain scans, DNS/DNSSEC and propagation lookups, WHOIS/RDAP, SPF/DKIM/DMARC/BIMI/MTA-STS and blacklist diagnostics through a keyless API. Also supports local DMARC report and raw-email parsing plus security-header generation.MIT
- AlicenseAqualityFmaintenanceProvides email validation and domain configuration auditing tools for AI assistants, enabling single address checks, bulk list cleaning, SPF verification, and full mail setup grading (A-F) with actionable fixes.448 npmMIT
TDQS
Scored across 19 tools
Each tool targets a distinct security check (SPF, DMARC, DKIM, MTA-STS, TLS-RPT, BIMI, DNSSEC, CAA, etc.), and the aggregate email_auth_audit is explicitly positioned as the entry point versus the per-record detail tools. Minor overlap exists between dns_lookup and mx_lookup, but descriptions clarify their different purposes.
Names are consistently snake_case and mostly follow a resource_check or resource_lookup pattern, which is predictable. A few deviations like email_auth_audit, reverse_dns, http_security_headers, and analyze_email_headers break the strict pattern but remain readable and recognizable.
19 tools is on the heavy side and exceeds the comfortable 15-tool threshold, though the breadth is somewhat justified by covering email authentication, DNS, TLS, web headers, WHOIS, and blacklists. It is not excessive enough to feel chaotic, but it is borderline for an MCP server.
For a read-only domain security auditor, the surface is remarkably complete: email authentication, DNSSEC/CAA, TLS certificates, HTTP security headers, WHOIS, blacklists, and email header forensics are all covered. The aggregate audit plus per-record detail tools form a coherent workflow with no major dead ends.