wazuh-daily-triage
Related Servers
Alternatives to wazuh-daily-triage
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAI-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.2813MIT
- AlicenseNot gradedqualityDmaintenanceBridges AI assistants with Wazuh SIEM infrastructure, providing natural language access to security alerts, vulnerability analysis, CVE databases, and network documentation for security operations.MIT
- AlicenseNot gradedqualityDmaintenanceAn 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
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Wazuh security alerts, investigate hosts, detect brute-force attempts, and generate security summaries by connecting to a Wazuh manager.-
- AlicenseBqualityBmaintenanceAn 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.2878 npm9MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Wazuh SIEM for alert querying, threat hunting, vulnerability scanning, and active response actions.MIT
TDQS
Scored across 18 tools
Most tools have clearly distinct roles, and the descriptions actively disambiguate the risky pairs (search_alerts = raw samples vs aggregate_alerts = counts vs rule_timeline = time histogram; logtest = current ruleset vs simulate_rule = draft replay). The cluster of alert-querying tools (search/aggregate/timeline/correlate/ip_profile) is the only place where an agent might briefly hesitate, but the guidance is strong enough that misselection is unlikely.
Names are all snake_case and readable, but the convention mixes verb_noun forms (list_environments, get_report, search_alerts, propose_knowledge, validate_rule_xml) with bare-noun resource names (inbox, knowledge, vulnerabilities, agent_info, rule_info, logtest, audit_report). It is not chaotic, but there is no single predictable pattern to infer a name from intent.
At 18 tools this is on the heavy side for a daily-triage server, though each tool maps to a plausible investigation axis (inventory, reports, alerts, enrichment, rule authoring). A few read-only lookups (list_environments, list_reports/get_report) could be merged without losing capability, so the surface feels slightly padded.
The surface covers the full triage loop: environment discovery, inbox/report review, alert search/aggregation/timeline, enrichment (agent, rule, IP, vuln, correlation), and a careful rule-authoring path (simulate, validate XML, propose). The main gap is proposal lifecycle: there is propose_knowledge but no tool to list/approve/reject or edit pending proposals, and no single-alert fetch-by-id beyond the 25-row search.