Skip to main content
Glama
Sign In
rison1337

x64dbg MCP

by rison1337
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to x64dbg MCP

No user-submitted related servers found.

    Related Servers

    • Rikune

      Last-emo-boy
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for reverse engineering Windows executables and related binary formats, offering static analysis, Ghidra-assisted function recovery, plugin-driven tooling, and optional isolated Windows runtime execution.
      11 npm
      240
      MIT

    • frida-mcp

      neeetman
      F
      license
      B
      quality
      D
      maintenance
      A simple MCP server exposing persistent, scriptable Frida dynamic instrumentation to an AI agent for Windows reversing, malware/security analysis, and dynamic debugging.
      19
      -

    • windbg_mcp

      276793422
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes WinDbg/cdb as a session-based debugging tool, allowing users to open dumps, launch/attach processes, and execute arbitrary cdb commands with persistent context across commands.
      -

    • IDA Pro MCP

      GrecAndrei
      A
      license
      Not graded
      quality
      B
      maintenance
      Deterministic, local-first MCP server for IDA Pro and IDA Home, exposing 109 strict-schema operations for reverse engineering with policy-gated mutations, evidence tracking, and broad AI-client support.
      15
      GPL 3.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 40 tools

    Disambiguation3/5

    Many tools are clearly distinct, but several clusters overlap: FindOEP, DumpModule, DumpPeFromMemory, and ValidateDump all concern dumping/unpacking, while GetDebugState, CaptureStopContextStructured, GetRegisterDump, GetCallStack, BridgeHello, GetSessionBinding, and EnsureReady expose overlapping state/health/session information. Descriptions clarify intended use, so selection is usually possible, but the boundaries are not always crisp.

    Naming Consistency4/5

    All tool names use PascalCase with no snake_case or camelCase mixing, and most follow a Verb+Object pattern such as GetModuleList, ReadMemory, and DumpModule. Minor deviations like MemoryWrite, BridgeHello, and EnsureReady are still readable, so consistency is good but not perfect.

    Tool Count2/5

    40 tools is heavy for this server. While a debugger and reverse-engineering automation domain can justify many capabilities, the surface splits some workflows across multiple overlapping tools and exceeds the 25+ threshold that the rubric treats as too many for the apparent scope.

    Completeness4/5

    The surface covers startup/attach, run control, memory, registers, modules/imports/exports, callstack, tracing, managed inspection, and dumping/unpacking. Gaps remain in breakpoint lifecycle, such as no standalone set/list/enable/disable tools, and no detach/restart/kill process control, but most can be worked around via existing state and capture tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources