Skip to main content
Glama

Related Servers

Alternatives to klaxon

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables conversational interaction with Wazuh SIEM, allowing users to investigate alerts, hunt threats, tune false positives, edit rules, and run security actions via natural language.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      AI-powered MCP server that enables security analysts to query Wazuh SIEM/XDR for alert triage, threat hunting, compliance audits, and incident response through natural language prompts.
      28
      13
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      An MCP server for the Wazuh SIEM/XDR platform that enables users to query agents, security alerts, detection rules, and decoders through Claude or other MCP clients. It provides specialized tools and prompts for investigating security alerts, performing agent health checks, and generating environmental security overviews.
      28
      17 npm
      4
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables querying and analyzing Wazuh security logs stored in OpenSearch, with features for searching alerts, getting detailed information, generating statistics, and visualizing trends.
      9
      2
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language security operations by connecting Wazuh SIEM to Claude Desktop via MCP, allowing querying of alerts, agents, vulnerabilities, and generating security reports with Slack integration.
      1
      -

    TDQS

    A4.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool covers a distinct operation: raw search, schema introspection, log decoding, manager passthrough, detector listing, test session listing, prebuilt findings summary, field coverage, GDPR classification, and posture check. search and findings_overview overlap somewhat, and schema vs field_coverage both address field population, but the descriptions clearly differentiate their scopes and outputs.

    Naming Consistency4/5

    All tool names use lower_snake_case and are descriptive, but there is no uniform verb_noun pattern: search is a bare verb, schema/manager/detectors are nouns, and others are noun+noun or noun+verb compounds. The style is consistent enough that names remain predictable, with only minor deviations from a stricter convention.

    Tool Count5/5

    Ten tools is well within the ideal range, and each serves a distinct investigative or compliance function. No tool feels redundant or superfluous, and the count matches the server's multi-faceted security analytics scope without becoming unwieldy.

    Completeness4/5

    The set covers the core Wazuh analysis lifecycle: querying, schema understanding, decoding, findings summarization, field population measurement, GDPR checks, and posture review. Notable gaps exist around detector lifecycle management (only list/get, no create/update/delete) and the manager passthrough is GET-only, though the descriptions explicitly justify these omissions as intentional.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues