An evidence case another party can inspect on its own.
An evidence case packages selected signed records, preserved native artifacts, and verification results so a separate recipient can inspect the same material without access to the source systems.
How evidence cases support compliance and audit review
This summary illustrates how findings may be presented. It is not a signed evidence bundle and cannot itself be cryptographically verified.
Reviewer conclusionsillustrative case
- question
- Was the paid MCP tool call delivered?
- established
- 4 conclusions
- missing
- 3 gaps
- not evaluated
- 4 open questions
One evidence case, with its gaps stated.
Verification separates what the supplied records establish from what is missing, conflicting, or not evaluated.
3 of 6 elements established. One is linked, one has stated limitations, and one was never supplied.
- Authorization referenceclient
- present
- Gateway decisiongateway
- signature verified
- MCP/API invocationtool server
- signature verified
- Payment-provider artifactpayment provider
- linked
- Delivery observationnot supplied
- missing
- Verification reportverifier
- complete with limitations
A customer questions a paid MCP tool call to a market-data service.
This scenario is illustrative. It intentionally includes missing evidence: a complete happy-path example would misrepresent what a real evidence case looks like.
- the supplied keys validate the gateway and tool-server signatures;
- the tool name and argument digest are bound by the tool-server record;
- the payment-provider artifact is linked to the case;
- the result artifact supplied for review matches its bound digest.
- independent delivery observation;
- recipient acknowledgment;
- evidence that every relevant retry was included.
- commercial liability;
- legal sufficiency;
- correctness of the underlying service result;
- whether the issuer omitted another event.