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 0.3 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.

Package installs cleanly, all 255 unit tests pass, both stdio and HTTP MCP server modes respond with valid initialize responses, CLI help/config/list-clients all work.

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

verdict
Runs with mocks
Argusic Score
82 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
12,326
forks
1,457
open issues
50
watchers
59
size
2 MB
created
last push

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.

  • ida-mcp-test command fails at import idapro: needs IDA Pro native library (libidalib.so) with IDADIR set
  • pip install -e .[dev] ignores [dependency-groups.dev] in pyproject.toml; dev deps not auto-installed
Install time
under a minute
Cold machine to finish
4 minutes
Errors hit and fixed
2 hit, 1 fixed with no human help
How the result was proved
pytest tests/ exited 0, 255 passed 117 subtests passed; curl POST to HTTP server returned 200 with valid initialize response; stdio initialize returned valid JSON-RPC response
Model tokens used
231,955
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.

| `ida-pro-mcp --help` | Prints usage |
| `idalib-mcp --help` | Prints usage |
| `ida-mcp-test --help` | Fails at `import idapro` (expected -- requires real IDA) |
| `ida-pro-mcp --list-clients` | Lists 24 MCP clients, detects Argusic Agent, Claude Code, Crush |
| `ida-pro-mcp --config` | Prints JSON config for stdio/streamable-http/SSE transports |
| `ida-pro-mcp` (stdio mode) | Responds to `initialize` with proper MCP capabilities |
| `ida-pro-mcp` (HTTP mode) | Listens on port, returns HTTP 200 with valid `initialize` response |
## Server Verification
- **Stdio**: Sent `{"method":"initialize"}` -- received valid `{"jsonrpc":"2.0","result":{"protocol…
- **HTTP**: Started server on port 18748 -- `curl -X POST /mcp` returned `HTTP 200` with proper `in…
## Mock Status
The `idapro` native library (`libidalib.so`) cannot be mocked at the Python level because it's a C …

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 0.3 minutes, faster than the median of the 48 comparable projects Argusic has measured.
  • Licensed MIT, 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.

Of the 49 ai projects Argusic has installed and timed, ida-pro-mcp was the 2nd fastest to reach a running state, and 38 of 49 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks82.000.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.

[![Tested by Argusic](https://argusic.com/badge/ida-pro-mcp.svg)](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 0 minutes, hitting 2 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. One attempt is 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.03: 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?
0.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 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?
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.
How does ida-pro-mcp compare with the alternatives?
Of the 49 ai projects Argusic has installed and timed, ida-pro-mcp was the 2nd fastest to reach a running state, and 38 of 49 reached one at all.
Where is the evidence for ida-pro-mcp?
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.

Discussion