Consumers cannot trust an SCS without proof it meets the requirements, so they should assess it against the adversaries it must resist (project contributors, project maintainers and SCS administrators) and at least its change management interface, control configuration and technical controls (read and write access lists, required approvals and approvers, organization change management rules), control plane, verifier and storage. The prompts cover who may approve changes and how non-text changes are rendered, how control configurations are protected from regression and from tampering by maintainers or administrators, administration and privileged access, whether controls work as intended, how provenance and VSAs are generated, development practices, management of cryptographic secrets, and protection of storage. An SCS may self-attest publicly or seek third-party certification.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.