mcp-hayabusa
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-hayabusaScan security.evtx for high-severity events"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-hayabusa
An MCP server that combines Hayabusa, the Rust-based Windows event log (EVTX) fast forensics and threat-hunting tool, with a small detection engineering knowledge base — so an LLM client like Claude Code can scan EVTX files, browse detection rules, and reason about ATT&CK coverage directly in conversation.
Point Claude at a .evtx file and ask it to find suspicious logons, lateral movement, or persistence activity — it drives Hayabusa under the hood and gets back structured JSON it can reason about. Or ask it "what detects T1003.001?" and it'll cross-reference this repo's curated Sigma rules against MITRE ATT&CK and tell you whether that technique is covered, partially covered, or a gap — and scaffold a new rule if it's a gap.
Tools
scan_evtx
Runs Hayabusa's json-timeline command against a single EVTX file and returns matched events as JSON.
Argument | Description |
| Path to the |
| Minimum severity to include: |
| Only include events whose rule title contains this substring (case-insensitive), e.g. |
|
|
| Caps the number of events returned. |
get_hayabusa_rules
Lists available Hayabusa/Sigma detection rules, optionally filtered by keyword — useful for discovering what detections exist, or for finding the right rule_filter value before calling scan_evtx.
Argument | Description |
| Only include rules whose title, description, or tags contain this substring (case-insensitive). |
| Caps the number of rules returned (default |
analyze_coverage
Reports whether this repo's curated Sigma rules (rules/) detect a given ATT&CK technique or tactic — each technique is covered (a detecting rule at or above the high severity threshold), partial (a detecting rule below it), or a gap (no detecting rule at all).
Argument | Description |
| An ATT&CK technique ID (e.g. |
suggest_rule
Checks coverage for an ATT&CK technique and, if it's not already covered, suggests how to detect it: a technique summary, log-source guidance for the relevant tactic, and up to three existing curated rules for sibling techniques to use as a style reference.
Argument | Description |
| ATT&CK technique ID, e.g. |
| If |
Related MCP server: mcp-hayabusa
Resources
Alongside the four tools above, the server exposes curated Sigma rules and ATT&CK technique metadata as MCP resources:
URI | Returns |
| All curated Sigma rules in |
| The raw Sigma YAML for one rule, addressed by filename stem. |
| Curated rules mapped to a given ATT&CK technique ID (e.g. |
| MITRE's technique metadata (name, description, tactics) plus this repo's coverage verdict for it — the same data |
Setup
1. Create a virtual environment and install dependencies
py -m venv .venv
.venv\Scripts\activate
pip install -r requirements.txt2. Download the Hayabusa binary and detection rules
py scripts/download_hayabusa.pyThis fetches the latest Hayabusa release for your platform from GitHub and extracts it into ./hayabusa/. The server expects the binary at hayabusa/hayabusa.exe on Windows (or hayabusa/hayabusa on Linux/macOS) — rename the downloaded, versioned binary (e.g. hayabusa-3.10.0-win-x64.exe) to that name if needed.
Detection rules are expected at hayabusa/rules/ (Hayabusa's own hayabusa and sigma rule sets). Clone them from the official rules repo into that path, e.g.:
git clone https://github.com/Yamato-Security/hayabusa-rules.git hayabusa/rules3. Download the ATT&CK technique lookup
py scripts/download_attack_data.pyThis fetches the MITRE ATT&CK Enterprise data and writes a compact technique_id -> {name, description, tactics, url} lookup to mappings/attack_techniques.json. It's gitignored and regenerated locally, so this step is required before analyze_coverage, suggest_rule, or the detection://attack/* resource will work. This repo's curated Sigma rules (rules/) are already checked in and don't need a download step.
4. Verify
py server.pyThe server communicates over stdio, so it won't print anything on success — it's ready for an MCP client to connect.
Connecting to Claude Code
This repo includes an .mcp.json with the server already configured:
{
"mcpServers": {
"hayabusa": {
"command": "py",
"args": ["server.py"]
}
}
}With this file present at the project root, Claude Code picks it up automatically when you open the project — no extra registration step needed. To add it manually to another project instead, run:
claude mcp add hayabusa -- py "C:\path\to\mcp-hayabusa\server.py"Once connected, ask Claude something like "Scan this EVTX file for high-severity events", "What Hayabusa rules cover lateral movement?", or "Do we have detection coverage for T1003.001?" and it will call scan_evtx, get_hayabusa_rules, analyze_coverage, or suggest_rule directly.
Requirements
Python 3.10+
Windows, Linux, or macOS (Hayabusa ships native binaries for all three)
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceEnables Windows Event Log (EVTX) analysis by wrapping Hayabusa, exposing scan and rule retrieval tools.Last updatedMIT
- Flicense-qualityBmaintenanceEnables scanning Windows EVTX event log files with Hayabusa, returning structured detection results through an MCP tool.Last updated
- Flicense-qualityCmaintenanceEnables EVTX (Windows Event Log) analysis via Hayabusa, providing tools to scan event logs and retrieve detection rules.Last updated
- Flicense-qualityBmaintenanceAnalyze Windows event logs (EVTX files) using Hayabusa, with tools to scan EVTX files for detections and list Hayabusa detection rules.Last updated
Related MCP Connectors
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/meg4tech/mcp-hayabusa'
If you have feedback or need assistance with the MCP directory API, please join our Discord server