MCP RE Server
Related Servers
Alternatives to MCP RE Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to analyze binaries, debug processes, and inspect kernel state using Ghidra, x64dbg, WinDbg, and ILSpyCmd.10Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides 7 reverse-engineering tools (hexdump, disasm, strings, xref, Ghidra decompilation, angr symbolic execution, OLLVM deobfuscation) for LLM agents like hermes-agent and Claude Desktop.1MIT
- AlicenseNot gradedqualityCmaintenanceA headless Ghidra server that enables AI agents to perform deep reverse-engineering tasks such as disassembly, decompilation, and patching via the Model Context Protocol. It supports extensive automation of analysis workflows in sandboxed environments through a catalog of over 200 specialized tools.196GPL 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to remotely execute scripts and query binary metadata and analysis results—strings, imports, exports, functions, disassembly, and searches—for reverse engineering and binary analysis tasks.-
- 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 gradedqualityCmaintenanceEnables AI agents to analyze and diff binaries by driving Ghidra headless or inside its GUI, exposing native reverse-engineering tools such as listing functions and segments, searching strings, decompiling, disassembling, and following cross-references. Ships with a devcontainer and supports local stdio or remote HTTP deployment.MIT
TDQS
Scored across 22 tools
Most tools target distinct resource+action pairs, but there is some overlap among binary analysis tools (analyze_binary, ghidra_analyze, radare2_analyze, pestudio_analyze) and between analyze_project and get_architecture_advice. Descriptions help differentiate them, so ambiguity is limited.
Naming conventions are inconsistent: verb_noun (analyze_project, execute_command), tool_prefix_action (ghidra_analyze, yara_scan), and noun_phrase (network_analysis, memory_forensics) are mixed. While tool_prefix is consistent within the RE tools, overall there is no single predictable pattern.
With 22 tools, the server is on the heavy side, and the mix of project development tools (scaffold_project, add_docker) with reverse engineering tools makes the scope feel broad. The count is within the 16-25 range but feels over-scoped for a supposed 'RE Server'.
The reverse engineering domain is well-covered: static analysis, dynamic analysis, memory forensics, network analysis, YARA scanning, and debugging. Minor gaps exist (e.g., no dedicated disassembly tool), but Ghidra/Radare2 handle that. The extra non-RE tools don't detract from RE completeness.