io.github.daedalus/mcp-reverse-engineering
A sandboxed MCP tool for reverse engineering with multiple tool integrations
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
mcp-reverse-engineeringclaude mcp add mcp-reverse-engineering -- uvx mcp-reverse-engineering==0.1.4
{
"mcpServers": {
"mcp-reverse-engineering": {
"command": "uvx",
"args": [
"mcp-reverse-engineering==0.1.4"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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
Frequently asked questions
What is io.github.daedalus/mcp-reverse-engineering?
A sandboxed MCP tool for reverse engineering with multiple tool integrations
How do I install io.github.daedalus/mcp-reverse-engineering?
It runs on your machine. In Claude Code: claude mcp add mcp-reverse-engineering -- uvx mcp-reverse-engineering==0.1.4. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.daedalus/mcp-reverse-engineering need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.daedalus/mcp-reverse-engineering open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.daedalus/mcp-reverse-engineering?
It is published by daedalus. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.