
Mcp Reverse Engineering
- 1 repo stars
- Updated May 3, 2026
- daedalus/mcp_reverse_engineering
io.github.daedalus/mcp_reverse_engineering is an MCP server that exposes sandboxed reverse-engineering tools to your coding agent.
About
io.github.daedalus/mcp_reverse_engineering is a Model Context Protocol server that wraps reverse-engineering capabilities in a sandbox so developers and small teams can delegate binary and binary-adjacent analysis to an AI agent without giving it free rein on the host machine. Install it when you are validating third-party CLIs, inspecting suspicious artifacts, or documenting how a closed binary behaves before you ship integrations. The server publishes as a PyPI identifier with stdio transport, which matches the usual local MCP workflow in Claude Code and Cursor. Expect intermediate-to-advanced comfort with RE concepts and tight scope: this is an agent tool chain, not a full IDA replacement or cloud lab. Skillselion lists it under Ship → Security so developers doing pre-release audits can find MCP servers beside skills and workflows in one journey-organized catalog.
- Sandboxed MCP server that isolates reverse-engineering tool calls from your main dev environment
- Stdio transport PyPI package (mcp_reverse_engineering 0.1.0.1) for Claude Code, Cursor, and other MCP clients
- Multiple integrated RE utilities exposed as MCP tools for agent-driven analysis sessions
- GitHub-hosted server schema aligned with MCP registry 2025-12-11
- Designed for builder-led security research—not a hosted SaaS RE platform
Mcp Reverse Engineering by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add mcp_reverse_engineering -- uvx mcp_reverse_engineeringAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | mcp_reverse_engineering |
| Transport | STDIO |
| Auth | None |
| Last updated | May 3, 2026 |
| Repository | daedalus/mcp_reverse_engineering ↗ |
What it does
Let your coding agent run reverse-engineering workflows inside a sandboxed MCP server instead of juggling local binaries by hand.
Who is it for?
Best when you want agent-assisted RE in a controlled stdio MCP setup.
Skip if: Skip if you need enterprise malware labs, GUI disassemblers only, or zero local Python/MCP setup.
What you get
After you register the server, your agent can call sandboxed RE tools through MCP with a clearer boundary between analysis and your everyday dev filesystem.
- MCP-registered reverse-engineering tool surface for agent sessions
- Sandbox-isolated invocation path for RE workflows
- Repeatable agent-driven analysis without manual tool chaining
By the numbers
- Server version 0.1.0.1 on PyPI identifier mcp_reverse_engineering
- Transport type stdio per MCP server.json
- Repository source GitHub daedalus/mcp_reverse_engineering
README.md
mcp-reverse-engineering
A sandboxed MCP (Model Context Protocol) tool for reverse engineering that provides a unified interface to various reverse engineering tools with security restrictions.
Purpose
This project provides a secure, sandboxed environment for executing reverse engineering tools via CLI or MCP protocol. It wraps common reverse engineering utilities (strings, objdump, readelf, binwalk, etc.) with safety features like filesystem isolation, timeouts, and argument validation.
Install
pip install mcp-reverse-engineering
Or for development:
pip install -e ".[dev]"
MCP Server Installation
To use as an MCP server with Claude Desktop:
mcp install src/mcp_reverse_engineering/server.py
Usage
CLI
# Extract strings from a binary
mcp-re --tool strings --file /path/to/binary
# Disassemble a binary
mcp-re --tool objdump --args "['-d']" --file /path/to/binary
# Analyze ELF headers
mcp-re --tool readelf --args "['-h', '-s']" --file /path/to/elf
# Run binwalk for firmware analysis
mcp-re --tool binwalk --file /path/to/firmware.bin
Python API
from mcp_reverse_engineering import ReverseEngineeringEngine
# Create engine with default config
engine = ReverseEngineeringEngine(
workspace="./workspace",
timeout=30,
)
# List available tools
print(engine.list_available_tools())
# Execute a tool
result = engine.execute_tool("strings", ["-n", "8"], "/path/to/binary")
print(result)
MCP Server
from mcp_reverse_engineering.server import mcp, strings, objdump, readelf, binwalk
# Run the server (stdio transport for Claude Desktop)
if __name__ == "__main__":
mcp.run()
API
ReverseEngineeringEngine
Main class for executing reverse engineering tools.
engine = ReverseEngineeringEngine(
workspace: str = "./workspace", # Sandbox directory
timeout: int = 30, # Tool execution timeout
config_path: str | Path | None = None, # YAML config path
)
Methods:
execute_tool(tool_name: str, args: List[str], file_path: Optional[str] = None) -> str- Execute a toollist_available_tools() -> List[str]- List enabled toolsget_tool_documentation(tool_name: str) -> Dict[str, Any]- Get tool docsget_mcp_tools() -> List[Dict[str, Any]]- Get MCP tool schemas
Available Tools
| Tool | Category | Description |
|---|---|---|
| file | file_tools | Determine file type |
| strings | file_tools | Extract printable strings |
| hexdump | file_tools | Hexadecimal dump |
| xxd | file_tools | Hexadecimal dump |
| objdump | binary_tools | Disassemble binary |
| readelf | binary_tools | Read ELF headers |
| binwalk | firmware_tools | Firmware analysis |
Development
# Clone the repository
git clone https://github.com/daedalus/mcp_reverse_engineering.git
cd mcp_reverse_engineering
# Install dependencies
pip install -e ".[test]"
# Run tests
pytest
# Format code
ruff format src/ tests/
# Lint
ruff check src/ tests/
# Type check
mypy src/
# Install pre-commit hooks
pip install pre-commit
pre-commit install
MCP Server Configuration
mcp-name: io.github.daedalus/mcp-reverse-engineering
Requirements
- Python 3.11+
- External tools: binwalk, radare2, ghidra, etc. (must be installed separately)
License
MIT
Recommended MCP Servers
How it compares
MCP integration for sandboxed RE tools, not a standalone disassembler skill or hosted cloud sandbox.
FAQ
Who is mcp_reverse_engineering for?
Developers using Claude Code or Cursor who need agent-driven reverse engineering with sandboxed MCP tool access.
When should I use mcp_reverse_engineering?
Use it during security review or integration hardening when you want the agent to invoke RE utilities without ad-hoc shell commands on your machine.
How do I add mcp_reverse_engineering to my agent?
Install the PyPI package mcp_reverse_engineering (stdio), point your MCP client at the published server entry, and restart the agent so the RE tools appear in the tool list.