RSigma
Related Servers
Alternatives to RSigma
AlicenseNot gradedqualityCmaintenanceAn MCP server that provides Sigma rule validation and configuration capabilities for AI assistants. It enables users to validate Sigma detection rules against various validators and manage validator configurations through MCP tools and resources.4MIT
Related Servers
- AlicenseAqualityAmaintenanceSigma detection rule writing, validation, and pySigma-based multi-backend conversion (Splunk, Elastic, Wazuh, Kibana) via 3 MCP tools and 3 Claude Code skills, backed by a 61-rule production corpus across 11 MITRE ATT\&CK tactic categories.32MIT
- AlicenseNot gradedqualityDmaintenanceUnifies 7,283+ detection rules from Sigma, Splunk ESCU, Elastic, and KQL into a single queryable interface via MCP, with a web dashboard and autonomous agent pipeline for detection engineering.331 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceAn MCP server that exposes a 60+ tool security and threat-intel stack to AI agents, enabling secret scanning, Sigma rule generation, ransomware lookup, OSINT, and deep research.1MIT
- AlicenseNot gradedqualityBmaintenanceReal security scanners for AI coding agents — SAST (441 rules), secret detection (419+ patterns), dependency CVEs (OSV.dev), MCP/skill vetting, MITRE ATT&CK. Open-source, Rust, free6 npmApache 2.0
- AlicenseAqualityAmaintenanceHigh-performance local MCP server and CLI written in Rust that scrubs 90%+ framework noise from AI debug logs with Tree-sitter AST validation and test rollback.56MIT
- AlicenseAqualityAmaintenanceMCP server exposing rlg (RustLogs) log files as tools for on-call / SRE agent workflows. Three tools over JSON-RPC stdio — tail_log (last N events, filtered by level/target), filter_log (predicate filtering), summarize_errors (grouped error taxonomy). Pure Rust. MIT OR Apache-2.0.36Apache 2.0
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes across parsing, validation, linting, conversion, evaluation, and pipeline inspection. The closest overlaps are lint_rules/fix_rules/validate_rules and test_exemplars/evaluate_events, but the descriptions give enough detail to distinguish their specific roles.
All tool names use snake_case with a verb-first pattern such as fix_rules, list_backends, parse_rule, and convert_rules. Minor noun variations like list_builtin_pipelines are still consistent with the overall convention.
Fifteen tools is within a reasonable range for a comprehensive Sigma rule toolkit and each tool covers a distinct stage of the rule lifecycle. No tool appears redundant or purely filler.
The surface covers parsing, validation, linting, auto-fixing, conversion to/from backend queries, event evaluation, exemplar testing, ADS scaffolding, tuning, and inspection of fields, backends, and pipelines. This gives full lifecycle coverage for Sigma rule authoring and analysis, with no obvious dead ends.