A sandboxed MCP tool for reverse engineering with multiple tool integrations
uvx mcp_reverse_engineeringAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-daedalus-mcp-reverse-engineering": {
"command": "uvx",
"args": [
"mcp_reverse_engineering"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
mcp_reverse_engineering is an MCP server for A sandboxed MCP tool for reverse engineering with multiple tool integrations. It supports STDIO transport.
Use the generated config in Install. This server runs with uvx mcp_reverse_engineering; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx mcp_reverse_engineering. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx mcp_reverse_engineering. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx mcp_reverse_engineering. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx mcp_reverse_engineering. Add required environment variables before starting Cursor or VS Code.
mcp_reverse_engineering uses STDIO transport. Use the package or command config in Install.
mcp_reverse_engineering inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
mcp_reverse_engineering does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
mcp_reverse_engineeringstdio | pypi | 0.1.0.1 | None advertised |