Tools changed (breaking): REA: Reverse Engineer Anything The REA: Reverse Engineer Anything MCP server, tested at version 6.9.0 on 2026-11-14 UTC, passed 3 of 5 real tool calls in a direct MCP stdio client test, with the two failures caused by optional local tools that were not installed, according to the review's scoring. The server's tools/list exposes 255 tools costing an estimated 68,233 tokens (cl100k_base, measured 2026-11-17 UTC), or 208% of a 32k context window and 34% of a 200k window, before any message is sent. The review scored the server 90/100, capped from 95 test points because not every real tool call passed, and notes 9 read versus 246 write (state-changing) permissions with no authentication. REA: Reverse Engineer Anything Before you use REA: Reverse Engineer Anything - Its 255-tool list is 68,233 tokens tools/list, cl100k base, measured 2026-11-17 UTC , which is bigger than many models' context windows. - 3 of 5 tool calls passed direct MCP stdio client, 2026-11-14 UTC, version 6.9.0 ; the 2 failures needed optional local tools we had not installed. Version 6.7.0 gave the same 3 of 5 on 2026-11-13 UTC. - Use it only on software you own or have permission to analyze. Context cost warning: its tools/list is about 68,233 tokens 255 tools , 208% of a 32k context window and 34% of a 200k window, before you send a single message. Load only the tools you need, or expect most of the context to go to tool definitions. Estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k base, measured 2026-11-17 UTC. How MCP context cost adds up https://testedmcp.com/guides/how-much-context-mcp-servers-cost/ 90 /100 Capped at 90: 3 of 5 real tool calls passed in our test; the tests add up to 95. Why scores are capped https://testedmcp.com/methodology/ pass-ratio Test points add up to 95; the score is capped at 90 because not every real tool call passed. Not a quality or security rating. Why scores are capped https://testedmcp.com/methodology/ pass-ratio Test points before the cap 95/100 - Install20/20 - Handshake30/30 - Maintenance25/25 - Docs10/15 - License10/10 Retested 2026-11-14 UTC at version 6.9.0, installed with npm --ignore-scripts: initialize and tools/list completed in about 0.5s on 3 of 3 runs 450-514 ms and listed 255 tools 207 at version 6.7.0 . GitHub stars: unverified see stars check in scored.json https://testedmcp.com/data/scored.json . Lawful use: Analyze only software you own or have permission to analyze. Tool-call test 2026-11-14 UTC, direct MCP stdio client, no LLM : pass core tools . 3 of 5 calls passed: objdump file headers and disassembly found main and open binary worked out of the box; inspect binary layout and list strings returned a clear provider unavailable error because they need optional local tools that were not installed. Same result as version 6.7.0 on 2026-11-13 UTC. Evidence: local test run, Nov 14, 2026 UTC. Transport tested 2026-11-14 UTC : stdio Tested version: 6.9.0 · tested 2026-11-14 UTC Token cost estimate : approx. 68233 tokens, cl100k estimate 255 tools, measured 2026-11-17 UTC, version 6.9.0 . This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k base. Permissions: 9 read, 246 write state-changing , 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown Auth: none. Rate limit: unknown. Pricing unit: unknown. - act on build computer — write state-changing - address name — write state-changing - address to file offset — write state-changing - analyze function — write state-changing - analyze javascript application — write state-changing - analyze swift types — write state-changing - analyze web bundle — write state-changing - annotate native function — write state-changing - audit release exposure — write state-changing - batch decompile — write state-changing - binary overview — write state-changing - binary session — write state-changing - build call path — write state-changing - build reconstruction obligation ledger — write state-changing - capture adb screen — write state-changing - capture browser scenario — write state-changing - capture electron scenario — write state-changing - capture native ui scenario — write state-changing - capture process scenario — write state-changing - capture web screenshot — write state-changing - check build task — write state-changing - close binary — write state-changing - close build computer — write state-changing - close frida session — write state-changing - close gdb session — write state-changing - close rizin debug session — write state-changing - collect adb bugreport — write state-changing - comment — write state-changing - compare application versions — write state-changing - compare artifacts — write state-changing - compare bundles — write state-changing - compare functions — write state-changing - compare javascript export shapes — write state-changing - compare managed members — write state-changing - compare process captures — write state-changing - compare source to bundle — write state-changing - compare static and observed endpoints — write state-changing - compare wasm interfaces — write state-changing - compare web captures — write state-changing - compare web screenshots — write state-changing - correlate static and runtime — write state-changing - current address — write state-changing - current document — write state-changing - current procedure — write state-changing - cutter command — write state-changing - decode android resources — write state-changing - decode interface builder — write state-changing - decode signal recording — write state-changing - decompile all — write state-changing - decompile jeb item — write state-changing - demangle swift — write state-changing - discover webmcp tools — write state-changing - evaluate reconstruction coverage — read - execute rizin command — write state-changing - export build environment — write state-changing - export environment bundle — write state-changing - export evidence bundle — write state-changing - export web scripts — write state-changing - extract artifact — write state-changing - extract firmware — write state-changing - find changed behavior — write state-changing - find xrefs to name — write state-changing - frida session status — write state-changing - gdb console — write state-changing - gdb session status — read - get call graph — write state-changing - get evidence bundle — read - get navigation context — write state-changing - get objc classes — write state-changing - get objc protocols — write state-changing - goto address — write state-changing - guided workflows — read - identify flutter build — write state-changing - import evidence bundle — write state-changing - import managed reconstruction — write state-changing - inline comment — write state-changing - inspect adb client — write state-changing - inspect adb device — write state-changing - inspect adb display — write state-changing - inspect adb package — write state-changing - inspect adb window — write state-changing - inspect address context — write state-changing - inspect analysis settings — read - inspect analysis view — write state-changing - inspect android class — write state-changing - inspect android jni bindings — write state-changing - inspect android method — write state-changing - inspect android package — write state-changing - inspect api contract — write state-changing - inspect apk signature — write state-changing - inspect apktool client — write state-changing - inspect apple ips — write state-changing - inspect artifact — write state-changing - inspect asset catalog — write state-changing - inspect binary hardening — write state-changing - inspect binary layout — write state-changing - inspect byte entropy — write state-changing - inspect dart aot — write state-changing - inspect desktop application — write state-changing - inspect devicetree — write state-changing - inspect electron fuses — write state-changing - inspect electron page — write state-changing - inspect elf notes — write state-changing - inspect elf unwind ranges — write state-changing - inspect erlang beam — write state-changing - inspect evm interface — write state-changing - inspect firmware regions — write state-changing - inspect go binary — write state-changing - inspect gpu code objects — write state-changing - inspect il2cpp metadata — write state-changing - inspect jeb client — write state-changing - inspect kernel build config — write state-changing - inspect kernel module — write state-changing - inspect keyed archive — write state-changing - inspect macho — write state-changing - inspect managed artifact — write state-changing - inspect managed members — write state-changing - inspect managed native boundaries — write state-changing - inspect model artifact — write state-changing - inspect native api — write state-changing - inspect native data type — write state-changing - inspect native dispatch metadata — write state-changing - inspect native exports — write state-changing - inspect native initializers — write state-changing - inspect native instruction — write state-changing - inspect native load image — write state-changing - inspect ntfs journal — write state-changing - inspect packet capture — write state-changing - inspect packet fields — write state-changing - inspect pcap capture — write state-changing - inspect pcap client — write state-changing - inspect pe certificates — write state-changing - inspect pe imports — write state-changing - inspect pe load config — write state-changing - inspect pe resources — write state-changing - inspect playwright trace — write state-changing - inspect plist — write state-changing - inspect python pyc — write state-changing - inspect recorded crash — write state-changing - inspect rust binary — write state-changing - inspect signal decoders — write state-changing - inspect signature — write state-changing - inspect sqlite database — write state-changing - inspect v8 code cache — write state-changing - inspect wasm artifact — write state-changing - inspect web event listeners — write state-changing - inspect web network capture — write state-changing - inspect web page — write state-changing - inspect windows shortcut — write state-changing - inspect with objdump — write state-changing - install adb package — write state-changing - instrument with frida — write state-changing - list adb devices — write state-changing - list adb directory — write state-changing - list adb features — write state-changing - list adb packages — write state-changing - list adb processes — write state-changing - list adb services — write state-changing - list architectures — write state-changing - list bookmarks — write state-changing - list browser targets — write state-changing - list cutter sessions — write state-changing - list documents — write state-changing - list electron targets — write state-changing - list frida devices — write state-changing - list frida processes — write state-changing - list javascript runtime targets — write state-changing - list jeb units — write state-changing - list names — write state-changing - list procedures — write state-changing - list segments — write state-changing - list strings — write state-changing - list unknowns — read - load frida script — write state-changing - mark build checkpoint — write state-changing - match native functions — write state-changing - measure build task — write state-changing - next address — write state-changing - observe javascript runtime — write state-changing - observe native calls — write state-changing - observe native ui — write state-changing - observe web execution — write state-changing - observe web session — write state-changing - open binary — write state-changing - open bundle resources — write state-changing - open jeb project — write state-changing - prev address — write state-changing - procedure address — write state-changing - procedure assembly — write state-changing - procedure callees — write state-changing - procedure callers — write state-changing - procedure info — write state-changing - procedure pseudo code — write state-changing - procedure references — write state-changing - project android application graph — write state-changing - project apple application graph — write state-changing - project harmony application graph — write state-changing - project managed application graph — write state-changing - pull adb file — write state-changing - pull adb package — write state-changing - push adb file — write state-changing - read adb logcat — write state-changing - read adb setting — write state-changing - read bytes — write state-changing - read function instructions — write state-changing - read guidance section — read - reconcile javascript runtime — write state-changing - record build consent — write state-changing - record unknown — write state-changing - recover javascript sources — write state-changing - reset investigation — write state-changing - resolve adb packages — write state-changing - resolve containing procedure — write state-changing - resolve native call targets — write state-changing - resume frida session — write state-changing - rizin debug command — write state-changing - rizin debug session status — write state-changing - search android classes — write state-changing - search bytes — write state-changing - search guidance — read - search procedures — write state-changing - search strings — write state-changing - set address name — write state-changing - set addresses names — write state-changing - set bookmark — write state-changing - set comment — write state-changing - set inline comment — write state-changing - start adb activity — write state-changing - start adb app — write state-changing - start build capture — write state-changing - start build computer — write state-changing - start frida session — write state-changing - start gdb session — write state-changing - start rizin debug session — write state-changing - stop adb app — write state-changing - stop build capture — write state-changing - trace android references — write state-changing - trace application feature — write state-changing - trace call path — write state-changing - trace dylib resolution — write state-changing - trace feature — write state-changing - trace javascript semantics — write state-changing - trace native ui action — write state-changing - trace native values — write state-changing - trace web module imports — write state-changing - trace web source location — write state-changing - uninstall adb package — write state-changing - unload frida script — write state-changing - unset bookmark — write state-changing - update analysis settings — write state-changing - update unknown — write state-changing - verify managed native boundaries — write state-changing - verify reconstruction — write state-changing - verify unknown resolution — read - xrefs — write state-changing handshake and tools listed without a recorded key or OAuth Score 90/100 · Tools 255 · Token cost approx. 68,233 tokens Tool list changed 2026-11-17 UTC; count from 2026-11-17 UTC capture · Compare https://testedmcp.com/compare/?s=rea-reverse-engineer-anything · Last tested 2026-11-14 UTC · Version tested 6.9.0 · Package rea-agents https://www.npmjs.com/package/rea-agents morluto/rea https://testedmcp.com/go/rea-reverse-engineer-anything/ Summary: REA: Reverse Engineer Anything completed an MCP handshake without credentials and exposed 255 tools. Evidence summary - Handshake - pass - Tools listed - 255 - Context cost - approx. 68233 tokens, cl100k estimate 255 tools, measured 2026-11-17 UTC, version 6.9.0; an estimate ranking https://testedmcp.com/best/lowest-context-cost-mcp-servers/ · add up your servers' context cost https://testedmcp.com/guides/how-much-context-mcp-servers-cost/ Tool list changed 2026-11-17 UTC; count from 2026-11-17 UTC capture - API key - No key needed for the tools we called - Tested - 2026-11-14 UTC Test results | Test | Result | Points | Evidence | |---|---|---|---| | install | pass | 20 | npm install rea-agents Node 20, Linux succeeded in 13s. | | handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 255 tools listed in about 0.5s on 3 of 3 runs 450-514 ms; 2026-11-14 UTC retest of version 6.9.0, npm --ignore-scripts . Version 6.7.0 listed 207 tools on 2026-11-12 UTC. | | maintenance | pass | 25 | Repo pushed 0 days before test; GitHub star count unverified. | | docs | partial | 10 | README over 3,000 chars; install instructions present. Check of the package's own README README shipped in npm package . | | license | pass | 10 | MIT OSI-approved . | Local-model readiness Token cost estimate : approx. 68233 tokens, cl100k estimate for 255 tools · about 833% of an 8k context. This is an estimate from our testing counted with cl100k base . Small-model friendly schema heuristic, not a model result : low . Not tested Small-model task runs: Not yet tested. What we tested and what we didn't Tested on 2026-11-14 UTC - Install from the registry - We connected with no credentials and asked for its tool list: it listed 255 tools Method details: MCP initialize then tools/list - Maintenance signals last push, archived/deprecated status - Docs README length, install and config example - License OSI-approved or not - Token cost estimate Not tested - Security: not audited no code review, no permission or data-flow analysis - Real tasks no functional task runs yet - Behaviour with real credentials or a real account - Performance, rate limits or load - Correctness of results beyond the listed tasks Methodology: how we test https://testedmcp.com/methodology/ . A high score means it installs and responds, not that giving it access to your data carries no risk. Known security issues Checked on 2026-11-17 UTC for version 6.9.0 against OSV, GitHub repository advisories. Scope: the package itself; dependencies not scanned. No published advisories found in OSV and GitHub advisories for rea-agents 6.9.0 as of 2026-11-17 UTC. This is not a security audit. Monthly roundup: MCP security issues, October 2026 https://testedmcp.com/security/2026-10/ . Tool list changes ↻ Tools changed breaking 2026-11-17 UTC Tool list changed since last test 2026-11-14 UTC → 2026-11-17 UTC : +48 added, 234 changed breaking . Confirmed by a re-run with the same arguments. Show the diff - Added: act on build computer - Added: audit release exposure - Added: check build task - Added: close build computer - Added: compare static and observed endpoints - Added: decompile all - Added: export build environment - Added: export environment bundle - Added: guided workflows - Added: inspect analysis settings - Added: inspect android jni bindings - Added: inspect api contract - Added: inspect apk signature - Added: inspect apple ips - Added: inspect binary hardening - Added: inspect byte entropy - Added: inspect desktop application - Added: inspect devicetree - Added: inspect elf notes - Added: inspect elf unwind ranges - Added: inspect erlang beam - Added: inspect gpu code objects - Added: inspect il2cpp metadata - Added: inspect kernel build config - Added: inspect kernel module - Added: inspect model artifact - Added: inspect native exports - Added: inspect native initializers - Added: inspect ntfs journal - Added: inspect pe certificates - Added: inspect pe imports - Added: inspect pe load config - Added: inspect playwright trace - Added: inspect python pyc - Added: inspect v8 code cache - Added: inspect windows shortcut - Added: mark build checkpoint - Added: match native functions - Added: measure build task - Added: open bundle resources - Added: read guidance section - Added: record build consent - Added: reset investigation - Added: search guidance - Added: start build capture - Added: start build computer - Added: stop build capture - Added: update analysis settings - Changed schema: address name - Changed schema: address to file offset - Changed schema: analyze function - Changed annotation: analyze function - Changed schema: analyze javascript application - Changed schema: analyze swift types - Changed annotation: analyze swift types - Changed schema: analyze web bundle - Changed schema: annotate native function - Changed schema: batch decompile - Changed annotation: batch decompile - Changed schema: binary overview - Changed annotation: binary overview - Changed schema: binary session - Changed schema: build call path - Changed schema: build reconstruction obligation ledger - Changed schema: capture adb screen - Changed schema: capture browser scenario breaking - Changed schema: capture electron scenario - Changed schema: capture native ui scenario - Changed schema: capture process scenario - Changed schema: capture web screenshot - Changed schema: close binary - Changed annotation: close binary - Changed schema: close frida session - Changed annotation: close frida session - Changed schema: close gdb session - Changed schema: close rizin debug session - Changed schema: collect adb bugreport - Changed schema: comment - Changed schema: compare application versions breaking - Changed schema: compare artifacts - Changed schema: compare bundles - Changed schema: compare functions - Changed schema: compare javascript export shapes breaking - Changed schema: compare managed members - Changed schema: compare process captures - Changed schema: compare source to bundle breaking - Changed schema: compare wasm interfaces breaking - Changed schema: compare web captures - Changed schema: compare web screenshots - Changed schema: correlate static and runtime - Changed schema: current address - Changed schema: current document - Changed schema: current procedure - Changed schema: cutter command - Changed schema: decode android resources - Changed schema: decode interface builder - Changed schema: decode signal recording breaking - Changed schema: decompile jeb item - Changed schema: demangle swift - Changed schema: discover webmcp tools - Changed schema: evaluate reconstruction coverage - Changed schema: execute rizin command - Changed schema: export evidence bundle - Changed schema: export web scripts - Changed schema: extract artifact - Changed schema: extract firmware - Changed schema: find changed behavior - Changed schema: find xrefs to name - Changed schema: frida session status - Changed schema: gdb console - Changed schema: gdb session status - Changed schema: get call graph - Changed annotation: get call graph - Changed schema: get evidence bundle - Changed schema: get navigation context - Changed schema: get objc classes - Changed schema: get objc protocols - Changed schema: goto address - Changed schema: identify flutter build - Changed schema: import evidence bundle - Changed schema: import managed reconstruction - Changed schema: inline comment - Changed schema: inspect adb client - Changed schema: inspect adb device - Changed schema: inspect adb display - Changed schema: inspect adb package - Changed schema: inspect adb window - Changed schema: inspect address context - Changed annotation: inspect address context - Changed schema: inspect analysis view breaking - Changed schema: inspect android class - Changed schema: inspect android method - Changed schema: inspect android package - Changed schema: inspect apktool client - Changed schema: inspect artifact - Changed schema: inspect asset catalog - Changed schema: inspect binary layout - Changed schema: inspect dart aot - Changed schema: inspect electron fuses - Changed schema: inspect electron page - Changed schema: inspect evm interface - Changed schema: inspect firmware regions - Changed schema: inspect go binary - Changed schema: inspect jeb client - Changed schema: inspect keyed archive - Changed schema: inspect macho - Changed schema: inspect managed artifact - Changed schema: inspect managed members - Changed schema: inspect managed native boundaries - Changed schema: inspect native api - Changed annotation: inspect native api - Changed schema: inspect native data type - Changed schema: inspect native dispatch metadata - Changed schema: inspect native instruction - Changed schema: inspect native load image - Changed schema: inspect packet capture breaking - Changed schema: inspect packet fields - Changed schema: inspect pcap capture - Changed schema: inspect pcap client - Changed schema: inspect pe resources - Changed schema: inspect plist - Changed schema: inspect recorded crash - Changed schema: inspect rust binary - Changed schema: inspect signal decoders - Changed schema: inspect signature - Changed schema: inspect sqlite database - Changed schema: inspect wasm artifact - Changed schema: inspect web event listeners - Changed schema: inspect web network capture - Changed schema: inspect web page - Changed schema: inspect with objdump - Changed schema: install adb package - Changed schema: instrument with frida - Changed schema: list adb devices - Changed schema: list adb directory - Changed schema: list adb features - Changed schema: list adb packages - Changed schema: list adb processes - Changed schema: list adb services - Changed schema: list architectures - Changed schema: list bookmarks - Changed schema: list browser targets - Changed schema: list cutter sessions - Changed schema: list documents - Changed annotation: list documents - Changed schema: list electron targets - Changed schema: list frida devices - Changed schema: list frida processes - Changed schema: list javascript runtime targets - Changed schema: list jeb units - Changed schema: list names - Changed schema: list procedures - Changed annotation: list procedures - Changed schema: list segments - Changed schema: list strings - Changed annotation: list strings - Changed schema: list unknowns - Changed schema: load frida script - Changed schema: next address - Changed schema: observe javascript runtime - Changed schema: observe native calls - Changed schema: observe native ui - Changed schema: observe web execution - Changed schema: observe web session - Changed schema: open binary breaking - Changed annotation: open binary - Changed schema: open jeb project - Changed schema: prev address - Changed schema: procedure address - Changed annotation: procedure address - Changed schema: procedure assembly - Changed annotation: procedure assembly - Changed schema: procedure callees - Changed annotation: procedure callees - Changed schema: procedure callers - Changed annotation: procedure callers - Changed schema: procedure info - Changed schema: procedure pseudo code - Changed annotation: procedure pseudo code - Changed schema: procedure references - Changed schema: project android application graph - Changed schema: project apple application graph - Changed schema: project harmony application graph - Changed schema: project managed application graph - Changed schema: pull adb file - Changed schema: pull adb package - Changed schema: push adb file - Changed schema: read adb logcat - Changed schema: read adb setting - Changed schema: read bytes - Changed schema: read function instructions - Changed annotation: read function instructions - Changed schema: reconcile javascript runtime - Changed schema: record unknown - Changed schema: recover javascript sources - Changed schema: resolve adb packages - Changed schema: resolve containing procedure - Changed annotation: resolve containing procedure - Changed schema: resolve native call targets - Changed schema: resume frida session - Changed schema: rizin debug command - Changed schema: rizin debug session status - Changed schema: search android classes - Changed schema: search bytes - Changed schema: search procedures - Changed annotation: search procedures - Changed schema: search strings - Changed annotation: search strings - Changed schema: set address name - Changed schema: set addresses names - Changed schema: set bookmark - Changed schema: set comment - Changed schema: set inline comment - Changed schema: start adb activity - Changed schema: start adb app - Changed schema: start frida session - Changed schema: start gdb session - Changed schema: start rizin debug session - Changed schema: stop adb app - Changed schema: trace android references - Changed schema: trace application feature breaking - Changed schema: trace call path - Changed annotation: trace call path - Changed schema: trace dylib resolution - Changed schema: trace feature - Changed annotation: trace feature - Changed schema: trace javascript semantics breaking - Changed schema: trace native ui action - Changed annotation: trace native ui action - Changed schema: trace native values - Changed annotation: trace native values - Changed schema: trace web module imports - Changed schema: trace web source location - Changed schema: uninstall adb package - Changed schema: unload frida script - Changed schema: unset bookmark - Changed schema: update unknown breaking - Changed schema: verify managed native boundaries - Changed schema: verify reconstruction - Changed schema: verify unknown resolution - Changed schema: xrefs - Changed annotation: xrefs Snapshot hash fingerprint of the tool list 2d88df27c717 : SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed. Raw test record JSON { "name": "rea-agents", "version": "6.9.0", "registry": "npm", "status": "working", "tested": "2026-11-14", "tools count": 255, "deprecated": false, "archived": false, "tests": { "install": "pass", 20, " npm install rea-agents Node 20, Linux succeeded in 13s." , "handshake": "pass", 30, "MCP initialize + tools/list over stdio succeeded with no credentials; 255 tools listed in about 0.5s on 3 of 3 runs 450-514 ms; 2026-11-14 retest of version 6.9.0, npm --ignore-scripts . Version 6.7.0 listed 207 tools on 2026-11-12." , "maintenance": "pass", 25, "Repo pushed 0 days before test; GitHub star count unverified." , "docs": "partial", 10, "README over 3,000 chars; install instructions present. Check of the package's own README README shipped in npm package ." , "license": "pass", 10, "MIT OSI-approved ." } } Install npx -y rea-agents mcp Pin the version we tested npx -y rea-agents@6.9.0 mcp tested 2026-11-14 UTC. Newer versions may differ and were not tested by us. { "mcpServers": { "rea-reverse-engineer-anything": { "command": "npx", "args": "-y", "rea-agents@6.9.0", "mcp" } } } Tools listed Showing 40 of 255 names: act on build computer , address name , address to file offset , analyze function , analyze javascript application , analyze swift types , analyze web bundle , annotate native function , audit release exposure , batch decompile , binary overview , binary session , build call path , build reconstruction obligation ledger , capture adb screen , capture browser scenario , capture electron scenario , capture native ui scenario , capture process scenario , capture web screenshot , check build task , close binary , close build computer , close frida session , close gdb session , close rizin debug session , collect adb bugreport , comment , compare application versions , compare artifacts , compare bundles , compare functions , compare javascript export shapes , compare managed members , compare process captures , compare source to bundle , compare static and observed endpoints , compare wasm interfaces , compare web captures , compare web screenshots . Show all 255 names act on build computer , address name , address to file offset , analyze function , analyze javascript application , analyze swift types , analyze web bundle , annotate native function , audit release exposure , batch decompile , binary overview , binary session , build call path , build reconstruction obligation ledger , capture adb screen , capture browser scenario , capture electron scenario , capture native ui scenario , capture process scenario , capture web screenshot , check build task , close binary , close build computer , close frida session , close gdb session , close rizin debug session , collect adb bugreport , comment , compare application versions , compare artifacts , compare bundles , compare functions , compare javascript export shapes , compare managed members , compare process captures , compare source to bundle , compare static and observed endpoints , compare wasm interfaces , compare web captures , compare web screenshots , correlate static and runtime , current address , current document , current procedure , cutter command , decode android resources , decode interface builder , decode signal recording , decompile all , decompile jeb item , demangle swift , discover webmcp tools , evaluate reconstruction coverage , execute rizin command , export build environment , export environment bundle , export evidence bundle , export web scripts , extract artifact , extract firmware , find changed behavior , find xrefs to name , frida session status , gdb console , gdb session status , get call graph , get evidence bundle , get navigation context , get objc classes , get objc protocols , goto address , guided workflows , identify flutter build , import evidence bundle , import managed reconstruction , inline comment , inspect adb client , inspect adb device , inspect adb display , inspect adb package , inspect adb window , inspect address context , inspect analysis settings , inspect analysis view , inspect android class , inspect android jni bindings , inspect android method , inspect android package , inspect api contract , inspect apk signature , inspect apktool client , inspect apple ips , inspect artifact , inspect asset catalog , inspect binary hardening , inspect binary layout , inspect byte entropy , inspect dart aot , inspect desktop application , inspect devicetree , inspect electron fuses , inspect electron page , inspect elf notes , inspect elf unwind ranges , inspect erlang beam , inspect evm interface , inspect firmware regions , inspect go binary , inspect gpu code objects , inspect il2cpp metadata , inspect jeb client , inspect kernel build config , inspect kernel module , inspect keyed archive , inspect macho , inspect managed artifact , inspect managed members , inspect managed native boundaries , inspect model artifact , inspect native api , inspect native data type , inspect native dispatch metadata , inspect native exports , inspect native initializers , inspect native instruction , inspect native load image , inspect ntfs journal , inspect packet capture , inspect packet fields , inspect pcap capture , inspect pcap client , inspect pe certificates , inspect pe imports , inspect pe load config , inspect pe resources , inspect playwright trace , inspect plist , inspect python pyc , inspect recorded crash , inspect rust binary , inspect signal decoders , inspect signature , inspect sqlite database , inspect v8 code cache , inspect wasm artifact , inspect web event listeners , inspect web network capture , inspect web page , inspect windows shortcut , inspect with objdump , install adb package , instrument with frida , list adb devices , list adb directory , list adb features , list adb packages , list adb processes , list adb services , list architectures , list bookmarks , list browser targets , list cutter sessions , list documents , list electron targets , list frida devices , list frida processes , list javascript runtime targets , list jeb units , list names , list procedures , list segments , list strings , list unknowns , load frida script , mark build checkpoint , match native functions , measure build task , next address , observe javascript runtime , observe native calls , observe native ui , observe web execution , observe web session , open binary , open bundle resources , open jeb project , prev address , procedure address , procedure assembly , procedure callees , procedure callers , procedure info , procedure pseudo code , procedure references , project android application graph , project apple application graph , project harmony application graph , project managed application graph , pull adb file , pull adb package , push adb file , read adb logcat , read adb setting , read bytes , read function instructions , read guidance section , reconcile javascript runtime , record build consent , record unknown , recover javascript sources , reset investigation , resolve adb packages , resolve containing procedure , resolve native call targets , resume frida session , rizin debug command , rizin debug session status , search android classes , search bytes , search guidance , search procedures , search strings , set address name , set addresses names , set bookmark , set comment , set inline comment , start adb activity , start adb app , start build capture , start build computer , start frida session , start gdb session , start rizin debug session , stop adb app , stop build capture , trace android references , trace application feature , trace call path , trace dylib resolution , trace feature , trace javascript semantics , trace native ui action , trace native values , trace web module imports , trace web source location , uninstall adb package , unload frida script , unset bookmark , update analysis settings , update unknown , verify managed native boundaries , verify reconstruction , verify unknown resolution , xrefs Tool history: captured Nov 17, 2026 UTC. All tool history https://testedmcp.com/changes/ . Quick config { "mcpServers": { "rea-reverse-engineer-anything": { "command": "npx", "args": "-y", "rea-agents", "mcp" } } } Add to config https://testedmcp.com/free-tools/mcp-config-generator/?s=rea-reverse-engineer-anything Opens the config generator with this server selected. Setup 1. Install. Run npm install rea-agents Node 20 . This is the exact command we ran on 2026-11-14 UTC. 2. Configure. Add the mcpServers entry below to your MCP client config. 3. Verify. Restart the client and check that tools/list returns tools 255 in our test . { "mcpServers": { "rea-reverse-engineer-anything": { "command": "npx", "args": "-y", "rea-agents", "mcp" } } } Test history - 2026-11-17 UTC: Tools changed breaking - 2026-11-14 UTC: Retested - 2026-10-24 UTC: New Related: Best dev MCP servers https://testedmcp.com/best/dev-mcp-servers/ · Which MCP servers use the most context? https://testedmcp.com/best/most-context-mcp-servers/ · Troubleshooting: Timeout, no response https://testedmcp.com/troubleshooting/mcp-server-timeout-no-response/ FAQ Is REA: Reverse Engineer Anything deprecated? No. rea-agents was not deprecated or archived when we last tested it on 2026-11-14 UTC. What replaces REA: Reverse Engineer Anything? Nothing; REA: Reverse Engineer Anything is not deprecated as of 2026-11-14 UTC. Does REA: Reverse Engineer Anything need an API key? No. It completed an MCP handshake with no credentials and listed 255 tools. Embed the badge Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.