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. It provides 20 tools for DNS zone management, record configuration, and server diagnostics with built-in protections like rate limiting and read-only modes.3911MIT
- 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
- 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
- FlicenseAqualityDmaintenanceMCP server for managing and analyzing Cloudflare DNS — zones, records, analytics, and DNSSEC.141-
- AlicenseNot gradedqualityBmaintenanceMCP server for Pi-hole v6.x that provides direct API proxying and composite tools for analyzing network devices, managing block/allow lists, local DNS records, and performing backups.MIT
TDQS
Scored across 39 tools
Each tool names a distinct resource and action: zones, records, cache, block lists, allow lists, apps, settings, and DNSSEC are cleanly separated. Even similar-looking tools like dns_remove_blocked and dns_flush_blocked differ clearly by single-item versus full-list scope.
The dns_ prefix plus verb_noun pattern is used consistently across nearly all tools, e.g. dns_list_zones, dns_create_zone, dns_delete_record, dns_install_app. A few names break the get_ convention, notably dns_zone_options and dns_dnssec_info, which keeps this from a perfect score.
39 tools is well beyond the ideal 3-15 range and even beyond the 16-25 heavy range. While the Technitium DNS surface is broad, several clusters like block lists, allow lists, cache, and zones could be consolidated into parameterized list/update tools without losing capability.
The toolset covers the core DNS lifecycle: zone and record CRUD, cache management, blocking/allowlisting, server settings, apps, logs, stats, and DNSSEC info. Minor gaps such as missing zone import and no explicit DNSSEC sign/unsign operation are workable around through dns_set_zone_options and existing read tools.