mcpField
R
REA + Ghidra Toolkit

REA + Ghidra Toolkit

Remote
github.comOther0Updated today

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

  1. 01Reproducible REA and Ghidra workflows
  2. 02Read-only PE32 inventory
  3. 03Delphi VMT and RTTI guidance
  4. 04Headless Ghidra export helper
  5. 05Analysis and handover templates
  6. 06Synthetic tests for included tools

Use cases

  1. 01Start an authorized PE32 static analysis
  2. 02Inspect imports and binary inventory
  3. 03Validate Delphi VMT candidates
  4. 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.

Endpointhttps://gitmcp.io/ethanhunt1981/rea-ghidra-toolkit/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

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 README

REA + Ghidra Toolkit

REA + Ghidra Toolkit — evidence-first analysis banner

GitMCP docs Glama MCP connector License Python Ghidra REA


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:

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

AreaWhat is insideGood next read
🧭 docs/Evidence-oriented, reproducible workflows and validation rulesworkflow.md
🩺 tools/Read-only PE32 inventory and VMT helperstools/pe_inventory.py
🧰 ghidra/Headless export helperExportDecompilation.java
🫙 templates/Private analysis and handover templatestemplates/analysis-log.md
🧪 tests/Synthetic, dependency-light teststests/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

GitMCP

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

Markdown supported

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.