Adversarial REA
Related Servers
Alternatives to Adversarial REA
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to locally analyze and reverse engineer binaries through a compact 12-tool MCP interface for triage, function discovery, disassembly/decompilation, cross-references, strings/imports, call graphs, memory reads, annotations, and binary diffs.1MIT
- FlicenseNot gradedqualityDmaintenanceA local, privacy-first MCP server that orchestrates Ghidra, Binary Ninja, x64dbg, and system tools to provide AI assistants with powerful binary analysis capabilities.-
- AlicenseAqualityCmaintenanceMCP server integrating Rizin reverse engineering, RzGhidra decompiler, and capa for binary analysis, enabling LLMs to open binaries, identify capabilities, extract function addresses, and decompile to C pseudocode.109MIT
- AlicenseBqualityCmaintenanceEnables local, evidence-first triage of native binaries by extracting bounded symbols, strings, sections, call sites, gadget candidates, and mitigation signals as MCP tools for agent-guided manual review. It also provides metadata-only inspection for carriers such as archives, WebAssembly, firmware, and scripts without claiming verified vulnerabilities.125MIT
- AlicenseAqualityCmaintenanceA 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.11180Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to inspect and reverse-engineer native binaries, JavaScript/Electron apps, Go and Rust binaries, WASM, EVM bytecode, SQLite databases, and recorded crashes through a single MCP interface that bridges tools such as Ghidra, Frida, Hopper, binwalk, and jadx. Returns evidence-backed findings—pseudocode, symbols, strings, imports, routes, IPC boundaries—so agents can explain behavior and build similar features.MIT
TDQS
Scored across 12 tools
Most tools target distinct analysis aspects, but analyze_binary is a broad superset that overlaps heavily with get_symbols, get_strings, check_security, get_sections, and get_headers. find_dangerous_patterns also duplicates parts of the string/security tools, so an agent may hesitate between aggregate and granular calls.
The names are consistently snake_case and mostly follow a verb_noun pattern (get_symbols, check_security, find_gadget_candidates, inspect_carrier). The bare verb 'disassemble' is a minor deviation, but the overall convention is predictable and readable.
Twelve tools is well within the expected range for a binary analysis server and appears appropriately scoped. Each tool maps to a recognizable analysis capability, even if some outputs overlap.
The surface covers core static binary analysis: metadata, headers, sections, symbols, strings, security mitigations, disassembly, calls, gadgets, and some containment/fixture inspection. Minor gaps remain, such as explicit cross-reference or call-graph analysis and byte-pattern search, but most workflows have an available path.