wazuh-mcp-server
Provides a Model Context Protocol (MCP) server that exposes Wazuh Manager and syscollector data (agents, ports, packages, processes, rules, rule files, and SCA results) as MCP tools, including an authentication tool to refresh JWT tokens used to call the Wazuh Manager API.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Claims 'Secure: JWT token management with automatic refresh' and provides WAZUH_* credentials via env vars, but does not document MCP-side access control, authorization scopes per tool, or logging/redaction behavior. WAZUH_PROD_SSL_VERIFY defaults to true but can be disabled; that increases risk if misconfigured. Rate limiting and protection against abusive queries are not described.
⚡ Reliability
Best When
You control the runtime environment (network access, secrets, and Wazuh credentials) and want an MCP tool interface for an LLM to reason over Wazuh data.
Avoid When
You cannot restrict access to the MCP server and Wazuh credentials, or you need strict guarantees around error codes, retry semantics, and pagination behavior beyond the stated defaults.
Use Cases
- • Ask an LLM questions about Wazuh-monitored infrastructure (agents status, listening ports, running processes)
- • Generate and validate incident context by pulling Wazuh rules and rule file content
- • Query syscollector data for forensic triage (packages/processes/ports per agent)
- • Automate security configuration assessment (SCA) lookups via natural language
Not For
- • Public internet deployment without network controls (it binds to a host/port and relies on operational security)
- • Use as a general-purpose Wazuh API client without understanding Wazuh permissions and data exposure
- • Use where you require documented rate-limit behavior, idempotency guarantees, or strong operational SLAs from the MCP layer
Interface
Authentication
README states JWT token management with automatic refresh and includes an AuthenticateTool to force JWT refresh. No user-facing MCP auth mechanism is described (i.e., who can call the MCP server).
Pricing
Self-hosted open-source (license shown as AGPL-3.0 in repo metadata; manifest snippet shows MIT but that is untrusted data). Costs are mainly infrastructure and Wazuh operations; no external pricing described.
Agent Metadata
Known Gotchas
- ⚠ MCP auth layer is not described; ensure access to the MCP endpoint is restricted (network/firewall, bind address).
- ⚠ Some tools can trigger expensive Wazuh queries (rules listing, syscollector queries per agent); use limit/offset and filtering parameters carefully.
- ⚠ Token refresh is exposed via AuthenticateTool; agents may need to call it when encountering auth failures.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for wazuh-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.