Skip to main content
Glama
dbnz-io

OpenCDR MCP

Official
by dbnz-io

Related Servers

Alternatives to OpenCDR MCP

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as editors to start and monitor missions, run the self-healing demo, list departments and blueprints, and approve tasks through the backend API. It also lets trusted departments discover and invoke explicitly granted external stdio or Streamable HTTP tools.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP-capable clients to inspect and manage Keycloak realms, users, clients, roles, and groups with layered security modes, realm allowlisting, protected realms, delete gating, dry-run, and audit logging.
      8
      260 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables users to aggregate, discover, and route remote MCP tools through a unified endpoint, with category-based access tokens, OAuth authorization, and admin management/analytics for self-hosted infrastructure.
      -

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: rules, detection lists, signals, logs, integrations, settings, IR roles, and IR actions. The only mild terminology overlap is rules vs. detection lists, but the descriptions explicitly clarify which tool to use.

    Naming Consistency5/5

    All tools use the opencdr_ prefix and snake_case resource_action convention, with consistent list/get/search/stats verbs. Minor exceptions like opencdr_status and lists_show remain readable and do not create confusion.

    Tool Count5/5

    Fourteen tools is well-scoped for a read-only observability and investigation server. Each resource has only the list/get/search/stats operations needed for its role, with no obvious padding.

    Completeness4/5

    The read-only investigation surface is broad: health, rules, lists, signals, logs, integrations, settings, and IR roles/actions are all covered. Gaps remain around write/update/delete operations and rollback execution despite rollback-eligible IR actions, plus single-selector search limitations that agents must work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues