Skip to main content
Glama
Sign In
stack-and-dns-mcp

stack-and-dns-mcp

by Mewnah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to stack-and-dns-mcp

No user-submitted related servers found.

    Related Servers

    • NEL VEIL MCP

      NELPROINC
      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
      89 npm
      MIT

    • trust-score

      Br0ski777
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with zero-cost, zero-dependency trust evaluation for domains, URLs, wallets, APIs, and IPs, returning a 0-100 score with SSL, DNS, WHOIS, security header, and content sub-scores, plus batch comparison to rank multiple targets.
      MIT

    • Trust Center, SOC 2 Compliance

      tobiaslofton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to audit company domains for Trust Center platforms, compliance certifications, disclosed sub-processors, DNS identity and security records, email hardening, and live status-page health. It supports single-domain and parallel batch audits with structured risk scores and GRC summaries.
      MIT

    • DnsGuard

      miketusa-ctrl
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: live tech inspection, live email/DNS verification, combined audit, historical lookup, bulk job lifecycle, and watch/alert lifecycle. The orchestration tool comprehensive_audit overlaps by design but is explicitly an aggregate of the two scan tools, so it is not ambiguous. Bulk and watch tools are separated by resource, preventing misselection.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun pattern such as list_watches, inspect_tech_stack, start_bulk_check, get_bulk_check, watch_domain, and unwatch_domain. The main deviations are domain_history (noun phrase) and comprehensive_audit (adjective_noun), which slightly break the convention but remain clear and readable.

    Tool Count5/5

    Twelve tools are well-scoped for a domain intelligence server covering single-domain scans, aggregation, history, bulk checks, and monitoring. Each tool has a necessary place in the workflow, with no obvious padding or missing control surface.

    Completeness4/5

    The set covers the core lifecycle well: live scans, combined audit, historical lookup, bulk job start/status/list/cancel, and watch/alert management. Minor gaps remain around explicit alert management and retrieving full detailed scan results by identifier beyond what domain_history or compact bulk pages provide, but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources