← Back to All Research Dispatches
DISPATCH #02 · PUBLIC BENCHMARK REPORTOCTOBER 2026

Benchmarking ReaShield Sovereign on @modelcontextprotocol/sdk, CodeJackRabbit & BoxFleet

Measured before and after results for three JavaScript bundles: static REA observations, selected literal exposure, export counts, and tested behavior. The SDK bundle preserved 178 public exports in the recorded run.

Run record (v1.1.0): Values below come from the recorded benchmark report and its archive manifest (SHA-256: 90551ecc44ebee1a8c3c09c5145a55b708b89ba538162c02c2fc99268b12352c). The static analyzer was rea-agents@6.7.0. Each target was bundled to one JavaScript entrypoint before analysis; these counts describe that bundle and this analyzer, not the entire repository or every possible attack.

1. Why We Benchmarked the Official Model Context Protocol (MCP) SDK

We built and analyzed selected ESM entrypoints from three projects. The source package sizes below provide context; the measured unit in the table is one bundle per project:

  • @modelcontextprotocol/sdk@1.32.1: The selected bundle exposed 178 exports and yielded 90,693 AST nodes in the baseline REA analysis. The source package contained 349 files.
  • CodeJackRabbit@0.3.0: High-performance polyglot security scanner with 168 exported symbols and 53,076 AST nodes.
  • BoxFleet@0.3.0: Cloud/local sandbox orchestrator with 40 ESM exports. Three native artifacts (Windows x64, Linux x86_64, macOS arm64) received separate static checks; this bundle benchmark did not qualify their runtime behavior.

2. Static Analysis Before and After

We ran rea-agents@6.7.0 analyze-javascript-application --format json on each baseline bundle and its protected counterpart. Return shapes and endpoints are REA graph observations. Literal counts are exact matches against a fixed list of 6 to 8 strings per target. A zero count does not prove that an agent could not recover the underlying behavior.

Bundle State AST nodes seen by REA Return shapes seen Endpoints seen Selected literals visible
MCP TypeScript SDK 1.32.1 Before90,6931917 / 7
After1,760 (-98.1%)000 / 7
CodeJackRabbit 0.3.0 Before53,07615588 / 8
After1,680 (-96.8%)001 / 8 remains visible
BoxFleet 0.3.0 Before5,6262706 / 6
After656 (-88.3%)000 / 6

3. Behavior and Timing Checks

The timing figures are single recorded runs, not repeated-sample latency estimates. The parity corpus exercised 4 scenarios for the SDK, 4 for CodeJackRabbit, and 2 for BoxFleet; export counts confirm presence of names, not individual behavior for every export.

BundleExports beforeExports afterScenarios matchedSimulation beforeSimulation afterProtection build
MCP TypeScript SDK1781784 / 44.056 ms3.089 ms466.24 ms
CodeJackRabbit1681684 / 44.633 ms1.628 ms385.86 ms
BoxFleet40402 / 20.387 ms0.274 ms174.86 ms

4. Interpretation

The static counts fell for all three selected bundles under this REA version. The fixed literal set was fully absent after protection in two bundles; one of eight CodeJackRabbit literals remained visible. The tested scenarios matched, and the recorded export names were present after protection. These observations do not establish complete source-code secrecy, broad behavioral parity, or resistance to all reverse-engineering methods.

Request Sovereign Access & Benchmark Audit ↗