Inspect the reply against the schema it promised. Every result here comes from a recorded public request.
node packages/cli/dist/cli.js contracts run --jsonRead-only. Exit 1 means a contract violation. Exit 2 means incomplete checks.01 / How the audit reads
From schema to repeat.
96 HTTP attempts. 99,684 ms elapsed. The line below tracks reading progress.
- 01
Read the contract
Take input and output schemas from the same tools/list snapshot.
- 02
Probe gently
Use small valid and invalid inputs. Space request starts by at least 500 ms.
- 03
Compare the reply
Keep undeclared fields. Check JSON text against structured content.
- 04
Repeat a failure
Send a fresh request within the 149-attempt ceiling. Retain both responses.
02 / Contract board
Open the evidence.
34 advertised tools. Select a row for its inputs, schema paths, offending values and raw replies.
34 of 34 tools shown
The material-generation operation is listed but not called. A missing schema or resource is not labelled as a contract violation.
03 / Trust material
A schema is not an attestation.
This is the published material. It has not been authenticated against a finalized chain state.
flop_trust_root
What the snapshot contains
- Version
- 2
- Snapshot hash
0xefffc5b29ba514f43cf05de5cd8a57206cf79044e629a023a00795f042dff8b7- dstackVkeys
[]
- No dstack verification keys were returned. A dstack quote cannot be checked against this response alone.
- Platform ids are shown as returned. This response does not provide a versioned id-to-platform-name mapping.
- A trusted signing root, signed platform collateral and a real quote bound to an inference session are still required.
flop_get_tcb_status
Check the advisory's date
Intel INTEL-SA-00219: original release 2019-11-12, last revised 2019-11-20. MCP latestTCB reports 2025-12-15.
The reported release date does not match Intel's advisory. Treat this TCB metadata as inconsistent, not as evidence that a platform is current. Tracked upstream in network #36.
securityAdvisories reports 2025-12-15 for the same id. Intel reports 2019-11-12.
The Intel reference is a dated snapshot of this advisory, not the complete current Intel PCS collateral set. Platform-specific TCB validity is not checked.
Existing TCB finding: network #36 ↗Dated sources
https://mcp.flop.network/mcp
2026-11-05 21:44:20 UTC
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00219.html
2026-11-05 21:44:19 UTC
https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2019/0xxx/CVE-2019-0117.json
2026-11-05 21:44:19 UTC
https://api.github.com/repos/flop-labs/network/issues/36
2026-11-05 21:44:20 UTC
What this does not verify
A matching schema does not prove semantic truth, model quality, payment finality or a cryptographic attestation. This audit samples safe inputs. It does not cover every possible request. The devnet can reset.
The quote verifier is simulated. Empty trust keys and inconsistent advisory dates cannot establish that an attestation is valid. The harness also needs public evidence before it can decide its UNVERIFIABLE claims.