Skip to main content
Glama
bgauger

Technitium Safe MCP

by bgauger

Related Servers

Alternatives to Technitium Safe MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run reconnaissance tasks such as DNS, WHOIS, certificate transparency, TLS certificate, HTTP header, and limited port checks against explicitly authorized domains and IPs. Scope permissions, deny rules, default-deny resolution pinning, rate budgets, and append-only audit logging are all enforced inside the server so an out-of-scope request cannot be expressed.
      12
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables DNS record lookups for types like A, MX, TXT, and CNAME, bulk queries of all major record types, and reverse DNS resolution from IP addresses to hostnames.
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to perform safe, read-only IT diagnostics and retrieve local runbooks, asset records, and knowledge articles through MCP, with allowlisted network checks and audit logging.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to perform network diagnostics and lookups, including subnet calculations, port and MAC vendor information, DNS and blocklist checks, TLS certificate inspection, and public IP discovery, all without needing an account or sending telemetry.
      11
      MIT

    TDQS

    D1.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools, server_health and dns_lookup, have clearly distinct purposes: one checks server status, the other performs DNS resolution. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow a consistent lowercase_with_underscores pattern, using noun compounds ('server_health', 'dns_lookup'). The style is uniform and predictable, though a verb_noun pattern is not used, consistency is maintained.

    Tool Count3/5

    With only 2 tools, the server is at the borderline of being too thin. While the tools are functional, they represent a minimal surface that may not justify a standalone MCP server for meaningful use.

    Completeness1/5

    For a DNS-related server, the tool surface is severely incomplete. Only health checking and basic DNS lookup are provided, with no support for managing zones, records, DNSSEC, or other essential DNS operations. This leaves major gaps for any typical DNS administration workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues