TheAICompanyLabs // Trust & Architecture Center

Zero-Subprocessor Security & Build Provenance

RCF v2.0-Antimatter is a 35MB compiled-Go local WebAssembly (Wasm) L7 execution boundary for Model Context Protocol (MCP) servers. It executes strictly inside your VPC, container, or developer workstation with 0 bytes of cloud egress—meaning zero new data subprocessors and zero DPA delays during enterprise security reviews.

1. Zero-Subprocessor Execution Architecture (0B Cloud Egress)

[MCP Client / Agent]
        │  JSON-RPC 2.0 (local stdio or MCP 2026-07-28 Streamable HTTP)
        ▼
┌───────────────────────────────────────────────────────────────────┐
│  RCF v2.0 Local Go/Wasm Boundary (Inside Your VPC / Host)         │
│  • Tool Schema Pinning (blocks post-approval tool-poisoning drift)│
│  • Parameter AST Sandbox (<1ms P50 via wazero Wasm)               │
│  • Local Tamper-Evident WORM Audit Log (Ed25519 / SHA-256 Merkle) │
│  • External Telemetry / Cloud Proxy Egress: 0 BYTES               │
└───────────────────────────────────────────────────────────────────┘
        │  Validated tool calls only
        ▼
[Target MCP Server / Internal API / Database]

Because prompts, tool arguments, credentials, and audit records never leave your environment, deploying RCF does not require adding TheAICompanyLabs to your public subprocessor list or triggering 30-day enterprise customer DPA notifications.

2. Explicit Technical Scope & Limitations

  • What RCF Deterministically Enforces: Pre-execution JSON-RPC tools/call parameter AST validation, path-traversal / shell-injection / obfuscated argument blocking, schema-hash pinning against tool-poisoning rug pulls (OWASP MCP01/MCP03/MCP05), sensitive-action gating, and local cryptographic WORM audit logging mapped to AIUC-1 Q4 2026, FINOS AIGF v3, and DORA requirements.
  • What RCF Does Not Claim to Solve: Deterministic AST parameter sandboxing does not inspect natural language reasoning drift inside syntactically valid, policy-allowed parameters, nor does it replace host OS kernel isolation or upstream OAuth 2.1 identity issuance.

3. Verifiable Releases (No Unverified curl | sh Required)

Security teams should never pipe unverified remote scripts into a shell. Inspect the open-source Go proxy core directly, verify SHA-256 release checksums and SBOMs, or build byte-reproducibly from source:

# 1. Inspect open-source proxy repository
https://github.com/TheAICompanyLabs/mcp-proxy-open-source
# 2. Verify SHA-256 checksum & GitHub build attestation before execution
shasum -a 256 -c checksums.txt
gh attestation verify rcf-proxy_* -R TheAICompanyLabs/mcp-proxy-open-source

4. Continuity & Bus-Factor Mitigation

  • Open-Source Core: Inspectable Go codebase under TheAICompanyLabs/mcp-proxy-open-source.
  • Source Escrow Option: Commercial and OEM customers receive private source-escrow continuity terms ensuring uninterrupted internal build rights.
  • Zero Runtime Lock-In: Local binary runs offline with no phone-home kill switch.

5. Standard Contracting & Compliance Roadmap

  • Common Paper Standard Terms: We contract on unmodified Common Paper Pilot, Design Partner, and Mutual NDA agreements to eliminate legal redlining.
  • Candid Compliance Status: Currently self-attested with full 0B-egress architecture & SBOM provenance; SOC 2 Type I audit and continuous third-party PTaaS scheduled for Q1 2027 (25–60 day fast-track).