GhidraMCP
MCP Server for Ghidra
Runs with mockssource: GitHubJavaApache-2.0commit 1e980252087b
Java, Apache-2.0 licensed.
GhidraMCP runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
The ghidra-mcp Python MCP server installs and runs in this container: pytest gives 19 passed (23 Ghidra-dependent skipped), and the streamable-http transport served working initialize/tools/list/tools/call requests (HTTP 200) through the full flow against the mock Ghidra backend, with the server logging a successful backend connection.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 82 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- 23 tests skipped: headless integration suite requires GHIDRA_INSTALL_DIR (Ghidra 12.1.4), the built extension jar, and Java 21, none of which exist in the container and no root to install30 minutes
- pytest not installed in venv (uv absent; README's pip path used instead)0.1 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- .venv/bin/python -m pytest -q returned '19 passed, 23 skipped in 4.64s'; ghidra-mcp --help printed usage exit 0; live streamable-http server answered initialize 200, tools/list 200 (30 tools), tools/call get_program_info and list_functions 200 against the mock backend
- Model tokens used
- 138,508
- Exact commit tested
- 1e980252087b
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
INFO: 127.0.0.1:41258 - "POST /mcp HTTP/1.1" 200 OK INFO:mcp.server.lowlevel.server:Processing request of type CallToolRequest Real end-to-end MCP exchange verified: `initialize` → `tools/list` (30 tools) → `tools/call list_fu… 2026-10-11T07:19:43.332625Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… exec /bin/sh -lc "pgrep -af '[g]hidra|[f]ake' || echo \"no leftover processes\"" in /work/repo succeeded in 0ms: no leftover processes All verification done and processes cleaned up. Summary: installed `ghidra-mcp` 2.0.0 into `.venv` … tokens used 138,508 All verification done and processes cleaned up. Summary: installed `ghidra-mcp` 2.0.0 into `.venv` …
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 3 minutes.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 2 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 82.00 | 0.03 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ghidramcp)Questions
- Does GhidraMCP run?
- GhidraMCP runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test GhidraMCP?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1e980252087b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test GhidraMCP?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does GhidraMCP take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does GhidraMCP need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing GhidraMCP?
- 2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for GhidraMCP?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.