crypto-reverse-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@crypto-reverse-mcp detect the encryption algorithm in this JS code"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
crypto-reverse-mcp
The missing "last mile" of JS reverse engineering. A Model Context Protocol (MCP) server that detects cryptographic algorithms, identifies obfuscation, reconstructs standalone implementations, generates SDKs, and bypasses anti-debugging — designed to complement browser-debugging MCP servers like js-reverse-mcp.
English | 中文
Why this exists
Existing JS-reverse MCP servers focus on browser debugging (breakpoints, network capture, script analysis). They help you find the encryption function. But they don't answer:
What algorithm is this? (AES? SM2? custom?)
Where does the key come from? (static? derived? from server?)
How do I reproduce it in Python?
How do I generate a complete SDK?
How do I bypass the anti-debugging that blocks my breakpoints?
crypto-reverse-mcp fills these gaps. It's a complement, not a replacement — pair it with js-reverse-mcp for the full workflow:
js-reverse-mcp: open page → find script → set breakpoint → capture I/O
crypto-reverse-mcp: identify algorithm → extract key → reconstruct Python → generate SDKRelated MCP server: PCM
Features
Tool | What it does |
| Identify AES/DES/RSA/SM2/SM3/SM4/HMAC/MD5/SHA + key/IV source + cipher mode |
| Detect webpack/JSFuck/AAEncode/obfuscator.io/packer/control-flow-flattening |
| Find S-boxes, initial hash values, round constants, curve parameters |
| Generate standalone Python/Node implementation from JS source + samples |
| Produce complete Python/Node/Go SDK with signing, login, error handling |
| Generate injection scripts to neutralize debugger loops, devtools detection, timing checks |
Quick Start
Claude Desktop / Cursor / VS Code Copilot
{
"mcpServers": {
"crypto-reverse": {
"command": "npx",
"args": ["-y", "crypto-reverse-mcp@latest"]
}
}
}Claude Code
claude mcp add crypto-reverse -- npx -y crypto-reverse-mcp@latestCodex CLI
codex mcp add crypto-reverse -- npx -y crypto-reverse-mcp@latestVS Code Copilot
code --add-mcp '{"name":"crypto-reverse","command":"npx","args":["-y","crypto-reverse-mcp@latest"]}'Requirements
Node.js 18+
Tool Details
detect_crypto
Input: JS source code (string)
Output: List of detected crypto usages with:
Algorithm name (AES, RSA, SM2, SM3, SM4, MD5, SHA-1, SHA-256, HMAC, PBKDF2, etc.)
Category (symmetric / asymmetric / hash / mac / kdf / encoding)
Library (CryptoJS, JSEncrypt, sm-crypto, node-forge, jsrsasign, WebCrypto, Node crypto)
Location (line:column) + code snippet
Confidence score (0-100%)
Key source (static string / variable / localStorage / cookie / app config)
IV source (for symmetric ciphers)
Cipher mode (CBC/ECB/GCM/CTR/CFB/OFB)
Padding (Pkcs7/ZeroPadding/NoPadding)
Detection methods:
Library API patterns (50+ regex patterns)
Web Crypto API / Node crypto module calls
Crypto constants (AES S-box, SHA-256 initial hash, SM3 IV, SM4 S-box, DES S-box, etc.)
Function name heuristics
identify_obfuscation
Input: JS source code
Output: Obfuscation type + confidence + unpack strategy
Detects: webpack-bundle, obfuscator.io, JSFuck, AAEncode, JJEncode, dean-edwards-packer, eval-loader, control-flow-flattening, string-array, dead-code-injection, minified, terser-minified
Each detection includes:
Confidence score
Evidence (what pattern matched)
Unpack hint (how to approach unpacking)
Deobfuscation strategy (step-by-step)
Recommended tools
extract_crypto_constants
Input: JS source code
Output: List of found crypto constants
Detects:
AES S-box / Inverse S-box / Rcon
SHA-256 initial hash values + round constants
SHA-1 initial hash values
MD5 initial values + T-constants
SM3 IV + Tj constants
SM4 S-box + FK + CK constants
DES S-box + IP permutation
SM2 / NIST P-256 curve parameters
CRC32 polynomial
Base64 alphabet
reconstruct_algorithm
Input: JS source code + optional input/output samples + target language
Output: Self-contained Python or Node implementation
How it works:
Detects algorithm type from source patterns
Extracts parameters (key, IV, mode, padding)
Generates implementation using standard libraries (pycryptodome, gmssl)
If samples provided, includes verification code
Supported algorithms: AES (CBC/ECB/GCM/CTR), DES, TripleDES, MD5, SHA-1, SHA-256, HMAC-SHA256, HMAC-MD5, RSA (PKCS1), SM2, SM3, SM4, Base64
generate_sdk
Input: API specification (URL, method, headers, sign spec, login spec) + target language
Output: Complete SDK file with:
Request construction with auto-signing
Crypto signature generation (HMAC/MD5/custom)
Login flow (with password encryption hook)
Error handling
Usage example
Languages: Python (requests), Node.js (http/https), Go (net/http)
bypass_anti_debug
Input: JS source code (optional) + techniques to bypass + output format
Output: Bypass injection script
Techniques:
debugger_loop— Neutralizedebuggerstatements in loopssetInterval_debugger— BlocksetIntervalcallbacks containingdebuggerdevtools_window_size— FixouterWidth - innerWidthdetectiondevtools_console_access— Prevent console object inspectiontiming_check— CapDate.now()/performance.now()deltasconsole_getter_trap— UndoObject.defineProperty(console, ...)function_toString_check— MakeFunction.toString()return native code
Output formats: inject_script (Tampermonkey/snippet), fiddler_rule (Fiddler OnBeforeResponse), chrome_devtools_snippet (DevTools Snippets)
Typical Workflow
1. [js-reverse-mcp] new_page → navigate to target site
2. [js-reverse-mcp] search_in_sources for "encrypt" / "sign"
3. [crypto-reverse-mcp] detect_crypto on found script → identify AES-CBC
4. [crypto-reverse-mcp] extract_crypto_constants → confirm S-box present
5. [js-reverse-mcp] set_breakpoint_on_text → capture input/output
6. [crypto-reverse-mcp] reconstruct_algorithm with samples → get Python code
7. [crypto-reverse-mcp] generate_sdk → complete API SDK
8. [crypto-reverse-mcp] bypass_anti_debug → if blocked by debuggerLocal Development
git clone https://github.com/crypto-reverse/crypto-reverse-mcp.git
cd crypto-reverse-mcp
npm install
npm run build
npm startDebug with MCP Inspector
npx @modelcontextprotocol/inspector node build/src/index.jsTest stdio communication
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}' | node build/src/index.jsConfiguration
No configuration required. All tools are stateless and work offline.
Comparison with other JS-reverse MCP servers
Feature | js-reverse-mcp | js-reverse-pro-mcp | mcp-reverse-server | crypto-reverse-mcp |
Browser debugging | ✅ | ✅ | ✅ | ❌ |
Breakpoints | ✅ | ✅ | ✅ | ❌ |
Network capture | ✅ | ✅ | ✅ | ❌ |
Hook framework | ❌ | ✅ | ❌ | ❌ |
Deobfuscation | ❌ | ✅ (Babel) | ✅ (AST) | ⚠️ (identify only) |
JSVMP analysis | ❌ | ❌ | ✅ | ❌ |
Crypto algorithm detection | ❌ | ⚠️ (keyword scan) | ⚠️ | ✅ (50+ patterns) |
Crypto constants extraction | ❌ | ❌ | ❌ | ✅ (S-box, IV, curves) |
Algorithm reconstruction | ❌ | ❌ | ❌ | ✅ (Python/Node) |
SDK generation | ❌ | ❌ | ❌ | ✅ (Python/Node/Go) |
Anti-debug bypass | ❌ | ❌ | ❌ | ✅ (7 techniques) |
Obfuscation identification | ❌ | ❌ | ❌ | ✅ (11 types) |
Use together for maximum coverage. crypto-reverse-mcp is designed to be complementary.
Roadmap
v0.2:
trace_crypto_chain— trace encryption from ciphertext back to plaintextv0.2: Improved minified code analysis (variable flow tracking)
v0.3: WASM crypto module detection
v0.3: Custom algorithm identification via I/O analysis
v0.4: Java SDK generation
v0.4: RPC-style API SDK generation (gRPC, GraphQL)
License
MIT
Available Tools
6 toolsbypass_anti_debugA
Generate anti-debugging bypass scripts for common anti-debug techniques. Detects and generates bypass for: debugger statement loops, setInterval debugger, devtools detection (window size, console access, Function.toString), timing checks, console.log getter traps, and CodeMirror/eruda detection. Input: JS source code or technique name. Returns bypass injection script + injection instructions.
Inputs: source, techniques, outputFormat.
detect_cryptoA
Detect cryptographic algorithms used in JavaScript source code. Identifies AES/RSA/SM2/SM3/SM4/HMAC/MD5/SHA family algorithms with evidence, key/IV source tracking, and cipher mode. Input: JS source code string. Returns list of detected crypto usages with algorithm type, location (line/col), evidence snippet, key source, IV source, and mode (CBC/ECB/GCM/CTR etc).
Inputs: source (required), options.
extract_crypto_constantsA
Extract cryptographic constants from JS source code. Identifies S-boxes (AES/DES), initial hash values (SHA-256/SHA-1/MD5/SM3), round constants, elliptic curve parameters (SM2/NIST curves), magic numbers, and known crypto constant arrays. Input: JS source code. Returns list of found constants with their crypto algorithm association and location.
Inputs: source (required).
generate_sdkA
Generate a ready-to-use SDK (Python/Node/Go) from a reversed API contract. Given endpoint URL, HTTP method, headers, body template, and the signature/encryption algorithm spec, produce a complete SDK file with: request construction, crypto signing, error handling, and usage example. Input: API spec (url, method, sign algorithm description, params). Returns SDK code in requested language.
Inputs: apiSpec (required), language.
identify_obfuscationA
Identify the obfuscation/packing technique used in JavaScript code. Detects webpack bundles, AAEncode, JJEncode, JSFuck, obfuscator.io, JavaScript obfuscator, babel minified, packer (Dean Edwards), UPX-style, eval-based loaders, and control-flow flattening. Input: JS source code. Returns obfuscation type, confidence, unpack hints, and recommended deobfuscation strategy.
Inputs: source (required).
reconstruct_algorithmA
Reconstruct a standalone implementation of a cryptographic algorithm from JS source + captured input/output samples. Given the original JS code and (optionally) sample input→output pairs, generate a self-contained Python implementation that reproduces the same transformation. Supports common AES/RSA/HMAC/MD5/SHA/SM2/SM3/SM4 patterns. Input: source code, optional samples (array of {input, output} pairs), target language (python/node). Returns reconstructed code + verification notes.
Inputs: source (required), samples, functionName, targetLanguage.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Hosted iOS app intelligence and creative research MCP server.
MCP server for static security analysis of Android source code
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
Related MCP Servers
- AlicenseCqualityBmaintenanceMCP Server for automated reverse engineering with IDA Pro.432,062 PyPI13,477MIT
- AlicenseBqualityFmaintenanceMCP server for reverse engineering that enables interaction with IDA Pro for analysis tasks such as decompilation, disassembly, and memory engagement reports.2446MIT
- 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
- 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.21-