Skip to main content
Glama
yup-21

Crash MCP Server

by yup-21
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Crash MCP Server

No user-submitted related servers found.

    Related Servers

    • Dynamic MCP Server

      42Research
      A
      license
      B
      quality
      A
      maintenance
      Enables crash dump analysis and kernel debugging by integrating the real crash utility with automatic dump discovery, kernel matching, and session management.
      7
      MIT

    • gdb-mcp

      traver88
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to control GDB debugger via MCP protocol for local and remote debugging, supporting CTF Pwn, crash analysis, and ELF inspection.
      13
      1
      MIT

    • WinDbg GUI MCP Server

      jianqiaojia
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the WinDbg GUI through the Model Context Protocol using a PyKD-based plugin integration. It supports executing debugger commands, inspecting registers, reading memory, and performing automated crash analysis via natural language.
      4
      -

    • WinDbgMCP

      mnemonic-re
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to drive live WinDbg/WinDbgX debugging sessions, including crash dump triage, live process attach, kernel debugging, multi-session management, and unrestricted debugger command execution with advanced reverse-engineering analysis 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

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_sys_info retrieves system info, list_crash_dumps scans for dumps, run_crash_command runs crash utility commands, run_drgn_command runs drgn Python code, start_session initiates analysis, and stop_session terminates it. The descriptions make it easy to differentiate between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_sys_info, list_crash_dumps, run_crash_command, run_drgn_command, start_session, stop_session). This uniformity makes the tool set predictable and easy to understand.

    Tool Count5/5

    With 6 tools, the server is well-scoped for crash analysis, covering essential operations like scanning dumps, running commands, managing sessions, and retrieving system info. Each tool earns its place without being excessive or insufficient.

    Completeness4/5

    The tool set provides strong coverage for crash analysis, including session management, command execution, and dump scanning. A minor gap exists in lacking tools for more advanced or specific analysis tasks, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources