Skip to main content
Glama
andsopwn

ida-fusion-mcp

by andsopwn

Related Servers

Alternatives to ida-fusion-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables large language models to read and write IDA Pro databases through structured tool calls for reverse engineering, binary analysis, and hook development. Provides broker-based routing, SQLite-backed static caching, multi-instance analysis, and both cached and live IDA API queries.
      66
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to autonomously inspect and control IDA Pro via MCP, providing tools for decompilation, disassembly, cross-references, renaming, typing, patching, searching, debugging, and arbitrary IDAPython execution.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to interact with IDA Pro databases and GUI, supporting reverse engineering tasks such as analyzing binaries and querying open files via natural language.
      6
      296 npm
      456
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to manage multiple isolated IDA Pro analysis sessions concurrently through a single MCP endpoint, allowing them to open, inspect, save, and close binary analysis sessions without launching multiple IDA windows.
      40
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-powered reverse engineering in IDA Pro by letting MCP clients inspect decompilation and disassembly, rename symbols, convert integers, and otherwise interact with the database through natural language.
      1
      MIT

    TDQS

    C2.6/5.0

    Scored across 66 tools

    Disambiguation2/5

    Many tools overlap in purpose, e.g., multiple ways to read memory (get_bytes, get_global_value, get_int, get_string, read_struct), multiple search tools (find, find_bytes, find_regex, search_text), and multiple debugging register tools. Agents would struggle to pick the right one.

    Naming Consistency2/5

    Naming conventions are mixed: some use verb_noun (list_funcs, find_bytes), some are verb-only (callees, imports), some use descriptive phrases (diff_before_after, survey_binary), and debug tools use a dbg_ prefix. No consistent pattern exists.

    Tool Count2/5

    66 tools is excessive for a binary analysis server. Many tools could be consolidated (e.g., memory-reading tools, debug register tools). The high count likely leads to agent confusion and inefficiency.

    Completeness4/5

    The tool surface covers most aspects of binary analysis: disassembly, decompilation, patching, debugging, type management, cross-references, and searching. Minor gaps exist (e.g., no standalone segment listing, no type renaming), but overall it is fairly complete.

    Maintenance

    ActivityNo data
    ResponsivenessWithin a week