ida-fusion-mcp
Related Servers
Alternatives to ida-fusion-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables 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.664MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI to manage multiple IDA Pro instances simultaneously by acting as a gateway, resolving port conflicts.1ISC
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with IDA Pro for reverse engineering and binary analysis, including running Python scripts, retrieving strings/imports/exports/functions, searching immediates/text/bytes, and getting disassembly.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to remotely drive IDA Pro for binary analysis, including executing Python scripts, listing strings, imports, exports, and functions, searching for immediate values, text, or byte sequences, and retrieving disassembly for address ranges.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with IDA Pro for reverse engineering and binary analysis by executing Python scripts, retrieving strings/imports/exports/functions, searching immediates/text/bytes, and getting disassembly.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to remotely control IDA Pro for reverse engineering and binary analysis, including executing Python scripts, retrieving strings/imports/exports/functions, searching values/text/bytes, and obtaining disassembly.-
TDQS
Scored across 66 tools
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 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.
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.
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.