Skip to main content
Glama
deenesjakoruzh
bgauger

Technitium Safe MCP

by bgauger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Technitium Safe MCP

許可されたTechnitium DNSサーバーに対する境界付き到達可能性チェックと明示的なDNSルックアップのための、特化した読み取り専用MCPサーバーです。アルファ版: テストは合成であり、実稼働中のTechnitiumデプロイメントとの互換性は認定されていません。

インストールと実行

Python 3.11+、uv、dig が必要です。

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

このプロセスはstdio上でMCPを話し、.env を読み込みません。サーバーエイリアス/ホストとプローブポートは許可リスト構成です。

Related MCP server: MCP IT Ops Server

安全性

Technitium APIや変更操作は公開されていません。サーバー数、ポート数/範囲、DNS名/タイプ、サブプロセスの実行時間、出力バイト数はすべて境界付きです。DNS名はオプション構文で始めることはできず、dig はシェルなしの固定引数ベクトルを受け取ります。監査データは境界付きですが、照会された名前を含みます。それに応じて保護してください。セキュリティ設計 を参照してください。

検証

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
NameRequiredDescriptionDefault
nameYes
serverNoprimary
record_typeNoA

Output Schema

NameRequiredDescription

No output parameters

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

server_healthD
NameRequiredDescriptionDefault

No parameters

Output Schema

NameRequiredDescription

No output parameters

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 2 tool updatesv0.1.0
    • First observeddns_lookup
    • First observedserver_health
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
ResponsivenessNo issues

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.
    297 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
    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

  • 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