About REA + Ghidra Toolkit
REA + Ghidra Toolkit is a reusable, evidence-oriented workflow and toolset for authorized static analysis of native PE32 binaries, especially 32-bit Delphi applications. It combines read-only inventory and VMT helpers with headless Ghidra export and documentation templates for traceable analysis.
Key features
- 01Reproducible REA and Ghidra workflows
- 02Read-only PE32 inventory
- 03Delphi VMT and RTTI guidance
- 04Headless Ghidra export helper
- 05Analysis and handover templates
- 06Synthetic tests for included tools
Use cases
- 01Start an authorized PE32 static analysis
- 02Inspect imports and binary inventory
- 03Validate Delphi VMT candidates
- 04Document findings for later analysis sessions
MCP support
The repository is listed in the MCP Registry and can be accessed through GitMCP as a remote, streamable HTTP server. The README does not specify particular tools or resources exposed to MCP clients.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit/mcpclaude mcp add --transport http ethanhunt1981-rea-ghidra-toolkit https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit/mcp{"mcpServers":{"ethanhunt1981-rea-ghidra-toolkit":{"type":"http","url":"https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit/mcp"}}}Open in Cursor{"servers":{"ethanhunt1981-rea-ghidra-toolkit":{"type":"http","url":"https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit/mcp"}}}Open in VS Code{"mcpServers":{"ethanhunt1981-rea-ghidra-toolkit":{"type":"http","url":"https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit/mcp"}}}{"mcpServers":{"ethanhunt1981-rea-ghidra-toolkit":{"serverUrl":"https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEREA + Ghidra Toolkit
A small, dependency-light toolkit for authorized static analysis of native binaries with REA and Ghidra. It is intentionally built as a reusable knowledge base for agents, not as a dumping ground for a specific target.
Think in two layers
- This repository contains only generic methods, tools, and synthetic tests.
- Every target-specific artifact, decompilation, or private result stays in the private analysis project.
When this applies
The toolkit is aimed at native, unmanaged PE32 binaries on Windows:
- classic 32-bit Delphi applications have dedicated guidance (VMT / RTTI);
- other PE32 code (e.g. C/C++ components) works with the read-only inventory and the headless Ghidra export;
- analysis is static only; every claim is verified before it is treated as a finding.
Not a fit for managed runtimes (.NET / Java), PE32+ 64-bit images (the quick parser is deliberately PE32-only), executing code as a debugging workflow, or any target without solid legal authorization.
Why this exists
You want to avoid rebuilding the same reverse-engineering workflow from scratch every time. This toolkit answers:
- How do I start a PE / Delphi analysis in a traceable way?
- How do I combine REA, Ghidra, and small local tools without treating inferences as facts?
- How do I export and document results so a later session can continue?
- Which mistakes should be avoided early instead of discovered late?
Repository layout
.
├── docs/
│ ├── workflow.md
│ ├── rea-ghidra.md
│ ├── delphi-pe32.md
│ ├── evidence.md
│ ├── troubleshooting.md
│ └── gitmcp.md
├── tools/
│ ├── pe32.py
│ ├── pe_inventory.py
│ └── delphi_vmt.py
├── ghidra/
│ └── scripts/ExportDecompilation.java
├── templates/
│ ├── analysis-log.md
│ └── handover.md
├── tests/
├── assets/
├── AGENTS.md
├── LICENSE
└── llms.txt
What you get
| Area | What is inside | Good next read |
|---|---|---|
🧭 docs/ | Evidence-oriented, reproducible workflows and validation rules | workflow.md |
🩺 tools/ | Read-only PE32 inventory and VMT helpers | tools/pe_inventory.py |
🧰 ghidra/ | Headless export helper | ExportDecompilation.java |
🫙 templates/ | Private analysis and handover templates | templates/analysis-log.md |
🧪 tests/ | Synthetic, dependency-light tests | tests/test_pe32.py |
Quickstart
# From the repository root
python -m tools.pe_inventory "C:\analysis\program.exe"
python -m tools.pe_inventory "C:\analysis\program.exe" --imports --json
# Check a known VMT candidate
python -m tools.delphi_vmt "C:\analysis\program.exe" --vmt 0x00412340
# Heuristic search; always validate candidates in a disassembler
python -m tools.delphi_vmt "C:\analysis\program.exe" --scan
Run the synthetic test suite:
python -m unittest discover -v
GitMCP
This repository is designed to be used with https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit.
It is also listed in the official MCP Registry as io.github.ethanhunt1981/rea-ghidra-toolkit (streamable HTTP via GitMCP; metadata in server.json).
OpenCode / typical agent setup:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"servers": {
"rea-ghidra-toolkit": {
"type": "remote",
"url": "https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit"
}
}
}
}
OpenCode CLI command:
opencode mcp add rea-ghidra-toolkit --global --url https://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit
opencode mcp list
Core rule
Observation, inference, and unknown are three different things. A plausible name, string, or VMT candidate is not yet a behavioral proof. The templates are here to keep that distinction visible across sessions.
License
This repository is licensed under the MIT License. The license covers the included methodology and tooling only. It does not cover original binaries, target-specific specifications, third-party protected material, or private analysis results.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.