Skip to main content
Glama
Sign In
deenesjakoruzh
Technitium Safe MCP

Technitium Safe MCP

by bgauger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Technitium Safe MCP

A focused, read-only MCP server for bounded reachability checks and explicit DNS lookups against allowlisted Technitium DNS servers. Alpha: tests are synthetic; compatibility with a live Technitium deployment is not certified.

Install and run

Requires Python 3.11+, uv, and dig.

uv sync --extra test
export TECHNITIUM_SAFE_SERVERS=primary=dns-primary.example.invalid
uv run technitium-safe-mcp

The process speaks MCP over stdio and does not load .env. Server aliases/hosts and probe ports are allowlisted configuration.

Related MCP server: MCP IT Ops Server

Safety

No Technitium API or mutation is exposed. Server count, port count/range, DNS names/types, subprocess duration, and output bytes are bounded. DNS names cannot begin with option syntax, and dig receives a fixed argument vector without a shell. Audit data is bounded but includes queried names; protect it accordingly. See security design.

Verify

uv run --extra test pytest
uv run python -m compileall -q src tests
uv build

MIT © 2026 Ben Gauger.

Available Tools

2 tools
dns_lookupD

Inputs: name (required), server, record_type. Returns: object

server_healthD

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    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

    ActivityStale
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • mcp-dns

      pipeworx-io
      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.
      137 npm
      MIT

    • MCP IT Ops Server

      m3yyyyy
      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

    • Technitium DNS MCP

      X1pheR
      A
      license
      Not graded
      quality
      B
      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

    • mcp-recon

      dotMuny
      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