MCPGate is the self-hosted deployment of the CAIN Trust Fabric (pre-production; no customer deployment, no third-party review). This page is a legacy index: several bundles below are withdrawn. The current, signed evidence with a clean-room verifier is at clawx.click/verify.html.
The former "156/156 conformance", "13/13 attacks" and "217/217 files" badges had no producing run and are withdrawn. What is measured: 49/49 synthetic attack self-tests written by CAIN (not an independent red team), and the signed claims registry, each claim with its status and limits.
Each legacy bundle is machine-readable. Withdrawn ones now say why, and give the hash of the original they replace:
WITHDRAWN 2026-09-21: the "156 assertions" figure had no producing suite.
Self-tests only: 49/49 synthetic vectors written by CAIN blocked (re-run 2026-09-28). Not an independent red team.
WITHDRAWN 2026-09-28: per-article "COMPLIANT" marks were self-scored. No notified or certification body has assessed CAIN.
WITHDRAWN 2026-09-28: the 948/1000 "AAA" profile was hand-written, not computed. No insurer is involved.
WITHDRAWN 2026-09-28: the 7.4 ms latency and ACTIVE flags were not measured. The code and its repository tests exist.
SUPERSEDED 2026-09-21: a live audit did not support this file. The current Byzantine evidence is in the proof fabric's BYZANTINE_PROOF_INDEX.
WITHDRAWN 2026-09-28: the 200/200 and 120/120 figures were never re-verified.
Sourced public vendor announcements. The earlier unsourced matrix was withdrawn 2026-09-21.
Withdrawn by the 2026-09-21 audit: the matrix was not supported by evidence. Kept only as history.
WITHDRAWN 2026-09-21: internal targets, not public proof. There is no audited customer revenue.
| Architectural Dimension | CAIN Studio (cainstudio.online) | MCPGate Sovereign (mcpgate.online) |
|---|---|---|
| Deployment Environment | Managed Multi-Tenant Cloud | Customer Private K8s / Air-Gapped Enclave |
| Network Boundary | Public HTTPS / Edge | Designed to run without outbound internet (not independently tested) |
| MCP Interceptor | Cloud API Proxy & Live Sandbox | Transparent stdio & HTTP sidecar proxy |
| Consensus Engine | Hosted Distributed Fabric | Local PBFT nodes (lab-tested; see the Byzantine index) |
| Telemetry Export | Live Cloud SSE Streams | Air-gapped CEF / LEEF / Signed JSON files |
1. Deploy the official Helm chart in your isolated cluster:
2. Verify health and BFT cluster consensus:
3. Run the conformance command (the old "156-point" figure is withdrawn; publish the raw output you get):
4. Execute adversarial self-red-team attack suite:
5. Verify cryptographic code and runtime provenance:
Try tool gating and SIEM event generation in the interactive sandbox (a demo, not production evidence; no latency figure is claimed here):