crypto-reverse-mcp
Related Servers
Alternatives to crypto-reverse-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn Model Context Protocol server that enables LLMs to autonomously reverse engineer applications by exposing Ghidra's decompilation and analysis tools. It allows AI agents to list code structures, rename methods, and analyze binaries directly through MCP-compatible clients.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceMCP server that enables agents to reverse engineer applications, from high-level behavior down to native binaries, using tools like Hopper and Ghidra.154 npm412MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for static .NET assembly analysis, offering decompilation, IL disassembly, metadata inspection, and protection detection tools without executing target assemblies.19-
- AlicenseBqualityFmaintenanceMCP server for reverse engineering that enables interaction with IDA Pro for analysis tasks such as decompilation, disassembly, and memory engagement reports.2446MIT
- AlicenseCqualityAmaintenanceMCP Server for automated reverse engineering with IDA Pro.431,061 PyPI12,013MIT
- AlicenseAqualityBmaintenanceA 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.11158Apache 2.0
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of JavaScript reverse engineering: crypto detection, obfuscation identification, algorithm reconstruction, anti-debug bypass, SDK generation, and constant extraction. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (detect_crypto, identify_obfuscation, reconstruct_algorithm, etc.), making them predictable and easy for an agent to navigate.
With 6 tools, the set is well-scoped for a specialized crypto-reverse MCP server. Each tool serves a clear purpose without unnecessary bloat or deficiency.
The tool surface covers core reverse engineering workflows: detection, identification, reconstruction, bypass, and SDK generation. A minor gap is the lack of a deobfuscation tool that actually transforms obfuscated code (beyond identification), but the set is otherwise complete for its stated domain.