ida-pro-mcp
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Runs with mockssource: GitHubhomepagePythonMITcommit fab3505ee240
Python, MIT licensed. The project labels itself: ai, aiagent, binary analysis, ida plugin, ida pro, mcp, mcp server and modelcontextprotocol.
ida-pro-mcp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 5 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
ida-pro-mcp package installs via uv sync, 255 standalone tests pass, the MCP server responds to initialize/ping over stdio and HTTP, and idalib-mcp/ida-mcp-test are blocked by missing IDA Pro libidalib.so
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 83.7 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.
- uv binary not on PATH; pip3 install uv needed2 minutes
- pip3 install rejected by PEP 668 externally-managed-environment guard1 minute
- idapro requires libidalib.so from a commercial IDA Pro installation; libidalib.so not present in container
- Install time
- 5 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- pytest tests/ -q exited 0 with '255 passed, 117 subtests passed' (15.1s); curl-like HTTP POST to /mcp returned status 200 with valid initialize result; stdio invocation returned valid initialize JSON-RPC response
- Model tokens used
- 78,099
- Exact commit tested
- fab3505ee240
- 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.
for l in lines:
if 'import' in l and ('idapro' in l or 'ida' in l.lower()):
print(f'idalib_server imports: {l.strip()}')
\" 2>&1" in /work/repo
succeeded in 0ms:
Python: 3.11.18
ida_pro_mcp imported OK
server module imported OK
All verification is complete. Here's the final report:
tokens used
78,099
All verification is complete. Here's the final report: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
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
- Took 5 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
- Hit 3 errors during setup, 1 of which were not solved.
Of the 235 ai projects Argusic has installed and timed, ida-pro-mcp was the 123rd fastest to reach a running state, and 166 of 235 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 85.33 | 0.08 | |
| Argusic Runner | 1/3 | Runs with mocks | 82.00 | 0.03 |
Topics (from GitHub)
aiaiagentbinary-analysisida-pluginida-promcpmcp-servermodelcontextprotocolreverse-engineering
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ida-pro-mcp)Questions
- Does ida-pro-mcp run?
- ida-pro-mcp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ida-pro-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fab3505ee240. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ida-pro-mcp?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ida-pro-mcp take to install?
- 5 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 ida-pro-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ida-pro-mcp?
- 3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ida-pro-mcp compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, ida-pro-mcp was the 123rd fastest to reach a running state, and 166 of 235 reached one at all.
- Where is the evidence for ida-pro-mcp?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.