Versioned profiles
Every profile identifies an exact r2mcp artifact, radare2 build, plugin inventory, decompilers, startup policy, limits, and selectable tools.
RADARE2 · MCP · CONTROLLED EXECUTION
Reverse engineering,
without ambient trust.
mcp.radare.org gives MCP clients a stable way to use radare2 through versioned analysis profiles, isolated runners, explicit tool policies, and revocable API keys.
MCP endpoint
/sseStreamable HTTPWHAT IT IS
One endpoint, reproducible analyzers.
The gateway separates public HTTP, account policy, and disposable analysis processes so an analyzer can be upgraded or replaced without taking the service down.
Least-privilege keys
Each API key is pinned to one profile and exposes only the tool subset you choose. Keys can expire or be revoked independently.
Replaceable runners
Wasm and native r2mcp backends run behind the gateway. They can live locally, in containers, or on remote workers with separate QoS.
WHAT YOU CAN DO
Bring radare2 tools to MCP clients.
Connect an MCP-capable assistant or development environment and expose only the analysis operations appropriate for the job.
- Inspectprogram information, functions, imports, and strings
- Analyzerun profile-approved radare2 analysis workflows
- Decompileuse the decompilers shipped by the selected profile
- Organizekeep uploaded binaries in simple project folders
- Controlchoose tools, expiration, quotas, and independent credentials
HOW IT WORKS
From account to MCP in three steps.
Choose a profile
Review the exact build, capabilities, tools, plugins, and decompilers available to your account.
Create a constrained key
Select only the tools your client needs and set a deliberate expiration date.
Connect your client
Use the generated bearer secret with /sse. Revoke it without disrupting your other clients.