Skip to main content
Glama

Related Servers

Alternatives to r2-copilot

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A multi-backend MCP server that exposes binary analysis capabilities from IDA Pro and Ghidra, allowing LLMs to directly drive reverse-engineering tools via natural language.
      11
      158
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A PyGhidra-based MCP server that exposes Ghidra's reverse engineering capabilities to AI agents, enabling binary analysis via tools like overview, search, view, list, edit, script execution, and version control.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An enterprise-grade MCP server for AI-powered reverse engineering. Enables AI agents to perform comprehensive binary analysis through natural language commands.
      156 PyPI
      203
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local, privacy-first MCP server that orchestrates Ghidra, Binary Ninja, x64dbg, and system tools to provide AI assistants with powerful binary analysis capabilities.
      Academic Free v1.1
    • A
      license
      Not graded
      quality
      A
      maintenance
      A Ghidra MCP server that enables AI language models to interact with Ghidra for reverse engineering tasks, providing small, context-efficient tools to reduce hallucination and handle large binaries.
      68 PyPI
      838
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that runs inside IDA Pro for AI tools, exposing reverse-engineering capabilities like function listing, decompilation, and analysis via HTTP.
      MIT

    TDQS

    C2.5/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, e.g. get_xrefs_to vs get_xrefs_from, search_bytes vs search_string vs search_rop_gadgets, and write_hex vs write_assembly vs write_nop. The generic execute_command overlaps with many specialized tools, and disassemble vs disassemble_function could be confused, but descriptions clarify scope.

    Naming Consistency5/5

    All tool names use predictable snake_case, with a consistent verb_noun or verb_object pattern throughout (e.g. create_session, list_functions, set_register, search_bytes). Minor verb variety reflects domain actions rather than naming inconsistency.

    Tool Count2/5

    At 43 tools, the surface is well above the typical 3-15 range and risks overwhelming an agent with many niche radare2 wrappers. Since execute_command already provides a raw fallback, some specific wrappers could likely be consolidated or omitted.

    Completeness3/5

    Core workflows are covered across sessions, analysis, disassembly, search, writes, and execution, but lifecycle gaps remain: no delete_breakpoint or disable_breakpoint, no delete_flag, and no call-stack/frame inspection. execute_command can work around these gaps, but the native tool surface is not fully complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues