Test evidence: ALL

Automated blindness test

The blindness test of the ALL 2.0.0 release gate, run on October 29, 2026 on macOS, Windows and Linux. A test client that talks like ChatGPT sent MCP requests with markers in the URL, headers, body, tool arguments and tool results, and in the OAuth token, through a test build of ALL's pass-through node that for this test ran on the same computer. The markers were searched for in everything that passed through the node. Result: 0 markers found; the positive control, a marker placed where the node can see it, was found every time.

File: e2e-proof.json
Date: October 29, 2026
Size: 14,791 bytes
SHA-256: 009cbfda49a4b87805d5d864a2f8ce4ce015b084db401e309ad37df6e39c5bcc

How to read it: under platforms, each system shows "result": "clean" and "positive_control": true; flows gives the TLS version, cipher and key exchange of each connection, and sources lists where the markers were searched (wire, node_tap, node_log), each with "findings": [].

Run with real ChatGPT: receipt

The receipt of the run with real ChatGPT on a Mac on October 26, 2026 (gate G0), done by hand with a 2.0 candidate: what was measured on the connection, the blindness capture (clean, with the marker present on the computer) and the limits of the run. Its limits, as the receipt states them: one operating system (macOS) measured, one ChatGPT client address observed, Windows and Linux not measured by this receipt, and it is the owner's observation, with no third-party audit.

File: g0-chatgpt-2026-10-26.json
Date: October 26, 2026
Size: 1,303 bytes
SHA-256: f026a4d1c1ce2f4c9e30421ab4f0f3200be5277339f0d109a4fc706c17fe93b8

How to read it: in observations, "tls_terminated_by": "device" means the TLS connection ended on the computer, followed by the TLS version, cipher and key exchange that were negotiated, the group ChatGPT offered first and capture 121641-0d72 as clean; limits lists what this run does not cover.

Run with real ChatGPT: TLS handshakes

The TLS handshakes of the same run, from capture 121641-0d72 taken on that run's test pass-through node (a cloud machine): what each client offered and what was chosen. Names and addresses of the test machine, and the address of an unrelated scanner, are redacted.

File: g0-handshakes-121641-0d72.txt
Date: October 26, 2026
Size: 3,103 bytes
SHA-256: bb28eb73995b4fc3e6c04f5886460cafe26711fe91c885571567767584cd90e2

How to read it: the four connections from 9.129.55.x, the ChatGPT address the receipt records (inside 9.129.0.0/16, which OpenAI publishes in openai.com/chatgpt-connectors.json, list of October 27, 2026), offered X25519MLKEM768 first and each got TLS1.3, TLS_AES_256_GCM_SHA384 and X25519MLKEM768; the other lines are the test machine's own cloud traffic and a scanner, as the file's header says.

DNS reading of all-mcp.app

A reading of all-mcp.app, the domain of each computer's own address, made on October 29, 2026 through the public resolvers of Cloudflare and Google.

File: dns-zone-all-mcp.app-2026-10-29.json
Date: October 29, 2026
Size: 1,213 bytes
SHA-256: 95bf976a0dab1ecfaf9c39f1d2f5076226da045ee72a0a33e378e3b7221caa47

How to read it: checks shows caa, dnssec and dns_only as ok; caa allows only letsencrypt.org with dns-01 and forbids wildcard certificates (issuewild ";"), ds is the DNSSEC record the domain registry publishes for the zone, and dns_only lists the public addresses of the pass-through nodes, none of them Cloudflare's.

SHA-256 list

The SHA-256 of the four files above in one file, in the format that shasum -a 256 -c reads.

File: SHA256SUMS.txt
Date: October 30, 2026
Size: 373 bytes
SHA-256: 13a2f6ca9f31f1ef5819b7ab59f32d1eba0fb257466d2483ab2acd7a4bb9f52b

How to read it: each line is a SHA-256, two spaces and the name of the file it belongs to.

How to verify

Download a file, compute its SHA-256 on your computer and compare it with the value on this page: they must be identical.

curl -O https://all-mcp.fyi/security/evidence/e2e-proof.json
shasum -a 256 e2e-proof.json

To check the four files at once, save them in one folder together with SHA256SUMS.txt and run shasum -a 256 -c SHA256SUMS.txt there: each file must say OK. On Linux, sha256sum gives the same values, and so does Get-FileHash -Algorithm SHA256 in PowerShell on Windows.

What was redacted

Only g0-handshakes-121641-0d72.txt was changed before publishing: the test machine's name, its private and public IP addresses, the address of an unrelated scanner, and the parts of host names that identify the machine and its cloud storage were replaced with [redacted]. The TLS versions, ciphers, key-exchange groups, ChatGPT's client addresses and the capture's SHA-256 are as recorded. The other three result files are published byte for byte as the release gate recorded them.

Test evidence