Mcp Reverse Engineering
Let your coding agent run reverse-engineering workflows inside a sandboxed MCP server instead of juggling local binaries by hand.
Overview
io.github.daedalus/mcp_reverse_engineering is an MCP server for the Ship phase that exposes sandboxed reverse-engineering tools to your coding agent.
What is this MCP server?
- 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
- 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
Community signal: 1 GitHub stars.
What problem does it solve?
Running reverse-engineering commands manually is risky, repetitive, and hard to audit when an agent needs iterative tool access.
Who is it for?
Indie builders and security-minded developers who want agent-assisted RE in a controlled stdio MCP setup.
Skip if: Teams that need enterprise malware labs, GUI disassemblers only, or zero local Python/MCP setup.
What do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
How it compares
MCP integration for sandboxed RE tools, not a standalone disassembler skill or hosted cloud sandbox.
Common Questions / FAQ
Who is mcp_reverse_engineering for?
Solo and indie builders 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.