Skip to main content
Glama
OrtaMarco

domain-security-mcp-server

by OrtaMarco

Related Servers

Alternatives to domain-security-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      47 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Domain 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.
      20
      555 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      4
      33 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables DNS and email security analysis through passive and active scanning capabilities. Provides comprehensive domain security checks including SPF, DMARC, DNSSEC validation, MX record analysis, and SMTP connectivity testing.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables targeted company discovery, real-time DNS MX deliverability diagnostics, and clean web Markdown extraction for AI agents.
      MIT

    TDQS

    A4.1/5.0

    Scored across 19 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues