Skip to main content
Glama
drmogie

Technitium MCP

by drmogie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Technitium MCP

No user-submitted related servers found.

    Related Servers

    • MCP Pi-hole Server

      aplaceforallmystuff
      A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to Pi-hole network-wide ad blocker, enabling monitoring of DNS traffic statistics, controlling blocking settings, managing whitelist/blacklist domains, viewing query logs, and performing maintenance tasks through natural language.
      16
      84 npm
      8
      MIT

    • pihole-mcp

      ranklancer
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and manage Pi-hole v6 DNS ad-blocker instances, including logs, allow/deny lists, groups, and stats. Supports multiple Pi-hole instances from a single endpoint.
      23 npm
      2
      MIT

    • Cloudflare MCP Server

      ry-ops
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage Cloudflare resources through natural language, including DNS records, zone management, Workers KV storage, cache purging, and analytics. Supports comprehensive Cloudflare operations with secure API token authentication.
      13
      2
      MIT
    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

    A3.5/5.0

    Scored across 11 tools

    Disambiguation3/5

    The generic technitium_call can invoke any endpoint, which overlaps heavily with the specialized wrappers (settings_get/set, blocking, flush_cache, zones, records, stats, resolve), so an agent may struggle to choose between the guided tool and the raw call. technitium_endpoints vs technitium_endpoint_help are also adjacent (discovery vs parameter lookup), though their descriptions distinguish them reasonably well.

    Naming Consistency4/5

    All tools share a clear technitium_ prefix in snake_case, which keeps them readable and grouped. However the suffix conventions are mixed: some use noun_verb ordering (endpoint_help, settings_get, settings_set) while others use verb_noun (flush_cache) or bare nouns (stats, zones, records).

    Tool Count5/5

    11 tools is well within the ideal 3-15 range and each tool maps to a distinct area of DNS server management (settings, blocking, cache, zones, records, resolve, stats, discovery). The set is cohesive without obvious filler.

    Completeness4/5

    Core lifecycle coverage is strong: read/write settings, blocking toggle, cache flush, zone listing, record list/add/delete, resolution, and stats, plus a generic call and endpoint discovery as an escape hatch for uncovered APIs. The main gap is in-place record update (only delete+add is documented) and no explicit user/permission or DHCP management, though the raw call partly compensates.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources