Reverse Engineering MCP server
A sandboxed MCP tool for reverse engineering with multiple tool integrations
1 stars42 downloads/wk
Reviews
Write oneNobody has reviewed Reverse Engineering yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Reverse Engineering tools (8, 7 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
binwalkwrite actionRun binwalk to find embedded files and code in a binary.
file_cmdwrite actionRun the file command to determine file type.
hexdumpwrite actionRun hexdump on a file to display its contents in hexadecimal format.
list_toolsList all available reverse engineering tools.
objdumpwrite actionRun objdump to disassemble and analyze binary files.
readelfwrite actionRun readelf to display ELF binary information.
stringswrite actionRun the strings command on a binary file to extract printable strings.
xxdwrite actionRun xxd on a file to create a hex dump.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan19 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 148 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Reverse Engineering compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,273 servers
- Tools
- 8
- the typical server has 7
- Tools that change things
- 88%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,534 servers
- Downloads a week
- 42
- more than 35% of 11,915 servers with a package
What its tools let an agent do: 1 read · 7 change
Install Reverse Engineering in Claude Code, Cursor or VS Code
claude mcp add mcp-reverse-engineering -- uvx mcp-reverse-engineering
What the publisher says
From the Reverse Engineering repository's README, as published. We do not edit it. Read it on GitHub
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-engineeringOr 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.pyUsage
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.binPython 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:
- executetool(toolname: str, args: List[str], file_path: Optional[str] = None) -> str - Execute a tool
- listavailabletools() -> List[str] - List enabled tools
- gettooldocumentation(tool_name: str) -> Dict[str, Any] - Get tool docs
- getmcptools() -> List[Dict[str, Any]] - Get MCP tool schemas
Available Tools
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 installMCP 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
Nothing above is checked by us. What we check is on the safety report.
Reverse Engineering: common questions
- Is Reverse Engineering MCP server safe?
- Mostly: it is graded B (82/100). Read the Reverse Engineering safety report
- How do I install Reverse Engineering?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Reverse Engineering need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Reverse Engineering maintained?
- The last commit was 183 days ago (2026-05-03). The latest release is v0.1.4.
- How does Reverse Engineering compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,273 servers); tools 8 (the typical server has 7); tools that change things 88% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.