Pocket Disasm
UnclaimedMulti-session IDALib MCP router for coding agents. Analyze multiple binaries in parallel with IDA-compatible reverse engineering tools.
Set up this server
More in AI & ML
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
8 of 8 tools
Documented tools (8)
From project documentation. A server handshake does not verify each tool’s description or behavior.
idb_close
Stop a worker and release its resources
idb_health
Read worker startup and process health
idb_list
List sessions, states, processes, and current selection
idb_logs
Read recent output from one worker
idb_open
Create an isolated session for a local binary
idb_save
Save the current IDA database
idb_select
Select a default session for the current MCP client
idb_wait
Wait for IDA auto-analysis and MCP startup
Tool change history
FAQ
Questions about Pocket Disasm MCP Server
- How do I connect Pocket Disasm MCP Server to Claude?
- The project does not publish a launch command that MCPVault could verify. Open the repository linked on this page for its install steps; the listing names Claude Code, Cursor, Windsurf as compatible clients.
- Is Pocket Disasm MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Pocket Disasm MCP Server do?
- Pocket Disasm MCP Server documents 8 tools to the agent, including idb_close, idb_health, idb_list. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.