Skip to main content
Glama
omeryemba

mcp-hayabusa

by omeryemba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-hayabusa

No user-submitted related servers found.

    Related Servers

    • mcp-hayabusa

      chiomao23
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables EVTX (Windows Event Log) analysis via Hayabusa, providing tools to scan event logs and retrieve detection rules.
      -

    • mcp-hayabusa

      TregardLabs-Dana
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables scanning Windows EVTX event log files with Hayabusa, returning structured detection results through an MCP tool.
      -

    • mcp-hayabusa

      SBecraft
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Windows event log forensics by wrapping Hayabusa, offering EVTX scanning, Sigma rule exploration, ATT&CK coverage analysis, and detection engineering resources.
      MIT

    • mcp-hayabusa

      msadigo
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to run Hayabusa detection scans over Windows event log (.evtx) files for forensic analysis and threat hunting.
      2
      MIT

    • mcp-hayabusa

      baobao26
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that wraps the Hayabusa CLI, enabling analysis of Windows EVTX event log files and browsing of its detection rule set.
      -

    • hayabusa-mcp

      Pirate-Kitty
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Windows Event Log (EVTX) analysis by wrapping Hayabusa, exposing scan and rule retrieval tools.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct task: rule updates, logon summary, version retrieval, keyword extraction, critical system detection, search, combined scan, coverage analysis, and rule suggestion. No two tools have overlapping purposes.

    Naming Consistency2/5

    Naming is inconsistent: six tools use the 'hayabusa_' prefix, while three (scan_evtx, analyze_coverage, suggest_rule) do not. Verb patterns also vary (e.g., 'update_rules' vs 'logon_summary').

    Tool Count5/5

    With 9 tools, the server is well-scoped for Windows event log analysis. Each tool addresses a specific need without redundancy or excessive granularity.

    Completeness4/5

    The surface covers rule management, detection, search, keyword extraction, system identification, and coverage analysis. Minor gaps exist (e.g., no dedicated tool to list all rules or export results), but core workflows are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources