Technitium MCP Secure
Related Servers
Alternatives to Technitium MCP Secure
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA security-hardened MCP server for managing Technitium DNS Server via its HTTP API, offering tools for DNS zones, records, blocking, cache, settings, and diagnostics.39MIT
- FlicenseNot gradedqualityDmaintenanceSafety-focused MCP server for querying and managing Technitium DNS Server through its HTTP API, with strict input validation and audit logging.12-
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseBqualityBmaintenanceA secure MCP server for managing Cloudflare DNS records, transform rules, page rules, and cache via natural language, with robust token handling and containerized deployment.26AGPL 3.0
- AlicenseAqualityAmaintenanceAn MCP server for managing Hetzner DNS zones and RRSets via the Hetzner Cloud API. It enables listing, creating, updating, deleting, importing/exporting zone files, and managing protection and TTLs from MCP clients.2250 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for managing AdGuard Home instances and AdGuardHome Sync with 33 tools across read, safe-write, and destructive operations, featuring three-tier write gating.23,439 npm2MIT
TDQS
Scored across 39 tools
All tools have distinct purposes, clearly differentiated by verb and noun. Even related tools like dns_flush_cache vs dns_delete_cached are scoped differently (entire cache vs specific domain). No ambiguity.
All 39 tools follow the dns_verb_noun pattern in snake_case. Verbs are imperative and descriptive, and the pattern is rigidly applied. Only very minor variations exist (e.g., dns_health_check vs dns_check_update), but they are still consistent overall.
39 tools is large but justified given the broad scope of DNS server management (zones, records, blocking, caching, apps, settings, stats, DNSSEC). Some tools could be consolidated (e.g., dns_allow_domain and dns_remove_allowed are separate, but that's acceptable). Slightly over the typical range but not chaotic.
The tool set covers virtually all common DNS operations: CRUD for zones and records, block/allow management, caching, apps lifecycle, settings, stats, DNSSEC, logging, and health checks. No obvious gaps for the intended purpose of managing a Technitium DNS server.