Skip to main content
Glama
SigmaLineage MCP

SigmaLineage MCP

by MohitDabas

βš”οΈ SigmaLineage MCP

Context-Aware EVTX Hunting Β· Lineage-First Triage Β· Zero Noise Tolerance

Python FastMCP Chainsaw Sigma


"A Sigma hit means nothing without its story. The process lineage chain is the story."


🎯 Why SigmaLineage?

EVTX triage in modern SOCs is a race against noise. You have millions of events, hundreds of alerts, and seconds to decide what's real.

πŸ” For the SOC Analyst

Generic alerts drown true incidents in false positives. You don't need more alerts β€” you need signal from noise.

SigmaLineage's rarity baseline engine automatically surfaces:

  • 🚨 Anomalous process-to-port connections

  • πŸ‘€ Suspicious user-log event signatures

  • 🌐 Weird URL lookups no one else made

Find the real threat. Fast.

🧬 For the Detection Engineer

A Sigma rule fires. But is it a sysadmin doing their job, or an attacker moving laterally?

The process lineage chain is our core moat.

SigmaLineage traces the full parent→child execution tree — up to 5+ generations — turning isolated alerts into a visual kill chain. You instantly see:

  • Was this cmd.exe spawned by services.exe or w3wp.exe?

  • Is rundll32 being launched from ProgramData?

  • Did WmiPrvSE.exe just spawn a reverse shell?

Stop chasing ghosts. Confirm the kill chain.


🧠 By combining rapid Sigma matching, automated lineage graphing, and multi-dimensional rarity baselining, SigmaLineage MCP transforms raw EVTX logs into actionable, context-rich intelligence β€” for AI agents and human analysts alike.


Related MCP server: EventWhisper

πŸ”§ Built On

Component

Role

src/sigmalineage_mcp/mappings/sigma-event-logs-all.yml

Chainsaw field-mapping definition

sigma_lineage.py

Process lineage runner script

src/sigmalineage_mcp/

FastMCP server orchestration


Tool Overview

1) run_sigma

Runs the Chainsaw Sigma hunt command and returns a summary of rule hits.

Inputs:

  • evtx_path (file or folder of logs to scan)

  • sigma_rules_path (directory containing Sigma rules)

  • mapping_path (Chainsaw mapping yaml, defaults to src/sigmalineage_mcp/mappings/sigma-event-logs-all.yml)

  • output_dir (directory where hunt.json is written)

Output Highlights:

  • hunt_json_path

  • hit_count

  • top_rules

  • top_source_files


2) run_sigma_lineage

Runs the Sigma hunt (or loads existing results) and traces the parent/child process lineage for hit processes.

Inputs:

  • All run_sigma inputs

  • levels (number of ancestor levels to trace, default 5)

  • skip_hunt (skip running Chainsaw hunt, loading existing hunt.json instead, default false)

Output Highlights:

  • hunt_json_path

  • process_lineage_json_path

  • process_lineage_md_path

  • sigma_hit_count

  • indexed_evtx_files

  • indexed_events

Example Lineage Highlights Output: Lineage Highlights


3) rare_events_baseline

Computes rare tuple combinations from parsed CSV event logs with baseline comparison to highlight anomalies.

Inputs:

  • target_csv_path (CSV file or folder to analyze)

  • baseline_csv_path (optional, defaults to target scope itself)

  • max_results (default 25)

  • max_baseline_count (filter threshold for baseline occurrence, default 2)

Tuple Families Analyzed:

  • process_dst_port_protocol: Maps unique combinations of process name, destination port, and protocol.

  • user_channel_event_id: Maps unique combinations of user, log channel, and event ID.

  • url_host_process: Maps unique combinations of accessed URL/domain, host computer, and initiating process name.

Example Rarity Baseline Analysis Output: Rarity Analysis


Folder Structure

sigmalineage-mcp/
  sigma_lineage.py            # Lineage tracer CLI script
  pyproject.toml              # Project configuration & dependencies
  README.md                   # This file
  src/
    sigmalineage_mcp/
      __init__.py
      __main__.py             # Standard script entrypoint
      config.py               # Paths configuration
      server.py               # FastMCP server orchestration
      mappings/
        sigma-event-logs-all.yml  # Chainsaw mapping file
      services/
        chainsaw_runner.py    # Subprocess runner for Chainsaw
        lineage_runner.py     # Subprocess runner for lineage tracer
        rarity.py             # Pure Python CSV rarity baseline engine

Installation

Prerequisites

  1. Chainsaw CLI: Ensure chainsaw is installed and available in your PATH (e.g. at ~/.local/bin/chainsaw).

  2. Python: Python 3.10+ is required.

Setup

From the repository root:

uv sync

Running the Server

Direct Execution

Start the FastMCP stdio server:

uv run sigmalineage-mcp

MCP Client Configurations

To wire this MCP server into different AI clients, use the standard JSON configuration snippet below, placing it in the tool-specific configuration file location.

Standard JSON Snippet

{
  "mcpServers": {
    "sigmalineage-mcp": {
      "command": "uv",
      "args": [
        "run",
        "--project",
        "/absolute/path/to/sigmalineage_mcp",
        "sigmalineage-mcp"
      ],
      "env": {
        "SIGMALINEAGE_PROJECT_ROOT": "/absolute/path/to/sigmalineage_mcp"
      }
    }
  }
}

Note: Replace /absolute/path/to/sigmalineage_mcp with the actual path where this repository is cloned on your system.

Client Configuration File Paths

  • Cursor: Add to the Cursor GUI settings panel (Settings -> Features -> MCP) or edit ~/.cursor/mcp.json (Linux/macOS) or %USERPROFILE%\.cursor\config\mcp.json (Windows).

  • Antigravity: Add to the mcp_config.json configuration file located at ~/.gemini/antigravity/mcp_config.json.

  • OpenCode: Add to ~/.config/opencode/opencode.json (Linux/macOS) or a project-level opencode.json file in the root of the repository.

  • Claude Desktop: Add to the global configuration file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    • Linux: ~/.config/Claude/claude_desktop_config.json

Available Tools

3 tools
rare_events_baselineC

Return rare tuple events with baseline frequencies from parsed CSV data.

Inputs: target_csv_path (required), max_results, baseline_csv_path, max_baseline_count. Returns: object

run_sigmaC

Run Chainsaw Sigma hunt and return hunt.json summary.

Inputs: evtx_path (required), output_dir (required), mapping_path (required), sigma_rules_path (required). Returns: object

run_sigma_lineageC

Run Sigma hunt + process lineage tracing and return process_lineage paths/summary.

Inputs: evtx_path (required), output_dir (required), mapping_path (required), sigma_rules_path (required), +2 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: one focuses on rare event baselines, another on Sigma hunts, and the third on Sigma hunts with lineage tracing. There is no overlap or ambiguity.

    Naming Consistency3/5

    The first tool uses a noun phrase pattern (rare_events_baseline), while the other two use a verb-noun pattern (run_sigma, run_sigma_lineage). This inconsistency in naming style may cause confusion for an agent.

    Tool Count4/5

    With 3 tools, the set is slightly small but well-scoped for the domain. Each tool serves a clear function without unnecessary bloat, fitting within the typical 3-15 range.

    Completeness4/5

    The tools cover the core workflows: baseline analysis, sigma hunts, and lineage tracing. There are minor gaps (e.g., no tool for managing rules or results), but the surface is complete for intended use.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides programmatic access to ingest and query Windows event logs (especially Sysmon logs), enabling security monitoring, incident response, and log analysis automation.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables fast, scriptable access to Windows .evtx event logs for incident response and digital forensics. Supports filtering events by time windows, Event IDs, and keywords with field projection to reduce output size.
      57
      GPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI-assisted Windows digital forensics analysis including parsing Windows Event Logs (EVTX), analyzing registry hives (SAM, SYSTEM, SOFTWARE), and remotely collecting artifacts via WinRM with built-in security queries and forensic reference data.
      55
      27
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language threat hunting and incident response by connecting LLMs to enterprise security data sources like Elasticsearch, EVTX logs, PCAP files, and Velociraptor.
      83 PyPI
      204
      GPL 3.0