MCP discovery
Inspect the approved MCP setup and tool-discovery contract. MCP is an integration interface, not the product or an authority boundary.
Open evaluation pathTechnical evaluation
A narrow technical surface for evaluating GENESIS.
Start with public-safe contracts and a synthetic workflow. ProofRelay records verification results for submitted evidence; it does not replace your source systems or give an integration permission to act.
API reference
Review the public capability and registry discovery contract before proposing an integration.
Open evaluation pathTechnology and trust
Understand what ProofRelay verifies, where verification stops, and why business authority remains explicit.
Open evaluation pathProduction remains a separate decision
Do not submit confidential data, credentials, customer documents, or production traffic to public endpoints. Tenant authorization, data handling, operational policy, and deployment readiness require a scoped review and independent evidence.
What is evaluated?
The evidence contract, configuration context, and result record should be identifiable without relying on an opaque success signal.
Who may act?
An evaluator should be able to distinguish a verifier response from the person or system authorized to take the next business action.
How does it recover?
A credible integration has a defined posture for retries, duplicate delivery, failed handoff, and later reconciliation.
Public evaluation status
Public claims are bounded by current runtime metadata.
Checking current status…