Everything IDA ships with,
already set up.

A stability-hardened build of ida-pro-mcp, packaged as single-tenant containers. Every instance is built from the same template and gets the full toolbox.

┌───┐ │▒▒▒│ └───┘

Full IDA Pro 9.4 + Hex-Rays

Commercial IDA with the decompiler. Every processor module and loader, xrefs, FLIRT and type libraries, licensed per instance.

▪▪▪▪▪ ▪▪▪▪▪ ▪▪▪▪▪

66 MCP tools

survey_binary one-shot triage. analyze_function returns pseudocode, callers, constants and xrefs for an address. Batch rename, type propagation, signature generation, multi-hop data-flow tracing.

┌───┐ │ >_│ └───┘

py_eval

Arbitrary Python inside IDA's own interpreter with Jupyter-style persistent locals. Variables from your last call are still there on the next one.

▛▀▀▀▜ ▌ ▪ ▐ ▙▄▄▄▟

Browser desktop

The full IDA GUI streamed to a tab with an agent panel docked beside it. No client install, no X forwarding, no VPN ritual.

↑ ┌┴┐ ▀▀▀

Direct upload

Drag a binary onto the dashboard and it lands in /opt/uploads with live progress and a 110MB ceiling. Open it from IDA's File menu the moment it arrives.

█▏ ▐█ █▏×▐█ █▏ ▐█

Air-gapped by default

No internet egress from instances. Outbound is dropped. Nothing you upload phones home, and nothing else on the host can see it.

the boring guarantees

The parts nobody puts on a landing page, because they only matter at 2am when a decompile has been running for eleven minutes.

hard numbersper instance
ida version9.4 + hex-rays x64
mcp tools66
upload ceiling110 mb
boot time~90 seconds
save budget600 s / db
tool timeout900 s
idle reap60 min
shell in your containeryes, via the agent
internet egressoff, ask to open
graceful shutdownsaves every db first
get access read the docs