borer
Related Servers
Alternatives to borer
- AlicenseCqualityBmaintenanceMCP Server for automated reverse engineering with IDA Pro.432,334 PyPI13,477MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for targeted binary analysis with Kuna, enabling listing and decompiling specific functions via natural language.2MIT
- FlicenseAqualityBmaintenanceEnables MCP clients to execute Python snippets and interact with Ghidra through its PyGhidra scripting environment via a local Java plugin.241-
- AlicenseNot gradedqualityCmaintenanceEnables agents to reverse-engineer software across native binaries, managed code, Electron apps, websites, and live runtime behavior, returning findings linked to the evidence and limitations behind each conclusion. It also maintains a durable workspace where those behaviors can be inspected, questioned, compared against real execution, and exported as runnable handoffs.371,123 npmMIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents (and a matching CLI) to inspect native binaries, JavaScript/Electron apps, .NET assemblies, Go/Rust/WASM artifacts, EVM bytecode, SQLite databases, recorded crashes, and websites without source code, explaining how features work and returning the evidence and limitations behind each conclusion. Analysis runs locally, using optional Hopper, Ghidra, or IDA providers for native targets.371,123 npmMIT
- AlicenseNot gradedqualityBmaintenanceConnects AI agents to reverse-engineering tools that inspect native binaries, JavaScript/Electron apps, .NET assemblies, websites, and runtime behavior without source code. Returns pseudocode, references, and evidence so agents can explain how a feature works or reimplement it.371,123 npm7MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to execute automated reverse engineering workflows by wrapping Ghidra's decompilation engine in a streamlined headless orchestration layer. It flattens native machine code into unified C exports while minimizing agent context waste.1MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect and decompile software they have no source for — Android APKs, Electron bundles, .NET assemblies, and Go, Rust or WASM binaries — plus adb device interaction, through a token-guarded Streamable HTTP MCP endpoint, stdio MCP, or a CLI. Ghidra-powered native binary decompilation can be opted in at startup for ELF, PE and Mach-O targets.6Do What The F*ck You Want To Public
TDQS
Scored across 34 tools
Descriptions explicitly scope each tool and cross-reference alternatives ('Not for X, use Y'), so close pairs such as decompile/disassemble, function/function_summary, and the string-focused tools are distinguishable. Minor overlap remains between query/script and binary_info/borer://triage, but not enough to cause misselection.
All names are lower_snake_case and mostly follow a query-by-resource-noun or action-verb_noun pattern, with no casing inconsistencies. There is some mixing of noun-style query tools (`functions`, `strings`) and verb-style operations (`load_binary`, `set_name`), but the convention remains logical and readable.
The server exposes 34 tools, which is heavy compared with the typical 3-15 range and feels overloaded. The broad reverse-engineering domain justifies many primitives, but several closely related variants could be parameterized or consolidated.
The static-analysis lifecycle is well covered: loading, inspecting, navigating, decompiling/disassembling, graphing, annotating, typing, saving/restoring and reloading. Gaps include no actual live-process tool despite descriptions referencing `live_read`, and no byte-patching or assembly operation.