Skip to main content
Glama

Related Servers

Alternatives to IDA Pro MCP

No user-submitted related servers found.

    Related Servers

    • 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
      274 npm
      1,177 PyPI
      275
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM clients like Claude to interact with IDA Pro for binary analysis, decompilation, cross-references, patching, and more via 41 MCP tools, 8 resources, and 7 guided prompts.
      52
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to perform binary analysis and reverse engineering via IDA Pro's headless idalib, providing 66 MCP tools like decompile, disasm, and xrefs without requiring the IDA GUI.
      2
      -
    • 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.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI-assisted reverse engineering in IDA Pro by providing tools to analyze binaries, decompile functions, manage comments, search patterns, and interact with the IDA database through natural language.
      56
      2
      MIT

    TDQS

    C2.7/5.0

    Scored across 66 tools

    Disambiguation2/5

    Several tools appear to duplicate each other: instance_list vs list_instances both list IDA instances, imports vs imports_query, list_funcs vs func_query, and xrefs_to vs xref_query cover overlapping ground. Analysis tools (analyze_function, analyze_component, analyze_batch, func_profile, survey_binary) also overlap heavily, making selection between them uncertain.

    Naming Consistency2/5

    The conventions are mixed: some tools are verb_noun (list_funcs, get_bytes, find_regex), others noun_verb (xrefs_to), others bare nouns (decompile, disasm, patch, rename, callees). The most glaring flaw is instance_list vs list_instances, the same concept with inverted word order.

    Tool Count2/5

    At 66 tools this is far above a comfortable surface, and a meaningful subset are redundant query variants (imports_query, func_query, xref_query, entity_query) or near-duplicate instance/signature helpers. The domain is broad but the count is inflated by overlapping tools rather than distinct capabilities.

    Completeness4/5

    The surface is remarkably thorough for binary reverse engineering: decompilation, disassembly, xrefs, callgraphs, read/write/patch of memory and code, stack frames, type declaration, signatures, comments, renaming, and cache management are all present. Only minor lifecycle gaps (e.g. segment-level operations, richer diffing) seem missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues