ProofRelay MCP setup
Connect verifiable agent actions in minutes.
ProofRelay exposes a read-only MCP verifier for agent builders. Use it to check verifier status, route checkpoint decisions, and verify non-confidential evidence bundles before relying on paid, governed, or real-estate workflow results.
Smithery-ready discovery facts
The canonical static server-card is live and should be the source of truth when any marketplace cache shows fewer than the full tool set.
Optional proof layer, not a default dependency
Connect ProofRelay when an agent action becomes worth proving. The public MCP helps builders plan and verify hash-only workflows without silently charging users or handling settlement.
Free builder layer
The public MCP is a read-only planning and verifier surface for non-confidential examples, hashes, bundles, replay plans, and receipt templates.
Use when actions matter
Best fit: autonomous jobs, paid MCP/API calls, delegated agents, external services, human approvals, and audit-sensitive workflows.
Skip trivial local work
For ordinary interactive coding, one-off local research, or simple file operations, ProofRelay can stay off until proof is worth the overhead.
Commercial path is separate
Paid verification, implementation help, private deployments, and enterprise support route through Stripe or GENESIS intake—not automatic MCP charges.
Invisible checkpointing for adoption
The easiest integration is a wrapper that records hash-only request, response, authority, and payment-context evidence behind high-value actions. Users see pass, fail, needs_review, or skipped; operators keep the bundle hash and verification hash for audit.
Expanded tool surface
Priority 1: paid action integrity
Payment proof normalization, bundle drafting, Stripe/x402 mapping, and replay planning.
Priority 2: MCP operator tools
MCP evidence wrappers, OpenAPI mapping, paid receipts, risk scans, and client helpers.
Priority 3: governance and audit
Human approval receipts, audit manifests, action logs, and vendor risk profiles.
Priority 4: real-estate proof packs
Title production, closing packs, wire/payoff review, lender conditions, and readiness signals.
All public MCP tools
If Smithery or a client cache shows only three tools, refresh from the static server-card and verify this full list before publishing copy.
- proofrelay.get_verifier_status
- proofrelay.recommend_checkpoint
- proofrelay.verify_bundle
- proofrelay.normalize_payment_proof
- proofrelay.build_bundle_draft
- proofrelay.describe_stripe_entitlement_flow
- proofrelay.adapt_x402_payment_proof
- proofrelay.plan_replay_rejection_test
- proofrelay.wrap_mcp_tool_evidence
- proofrelay.map_openapi_operation_evidence
- proofrelay.generate_paid_tool_receipt
- proofrelay.scan_mcp_risk
- proofrelay.describe_cli_sdk_helper
- proofrelay.build_human_approval_receipt
- proofrelay.build_audit_pack_manifest
- proofrelay.summarize_agent_action_log
- proofrelay.review_vendor_risk_profile
- proofrelay.build_title_production_evidence
- proofrelay.build_closing_proof_pack
- proofrelay.review_wire_payoff_change
- proofrelay.map_lender_condition_evidence
- proofrelay.compute_readiness_signal
- proofrelay.adapt_agent_identity_evidence
- proofrelay.build_registry_entry
- proofrelay.issue_conformance_badge
- proofrelay.verify_signed_attestation
Smithery CLI
Use the verified Smithery listing and then confirm all tools.
npx -y smithery mcp add genesis/proof-relay
npx -y smithery mcp get proof-relay
npx -y smithery tool list proof-relay
npx -y smithery tool call proof-relay proofrelay.get_verifier_status '{}'Claude Desktop / generic MCP JSON
Use streamable HTTP. No user API keys are required.
{
"mcpServers": {
"proofrelay": {
"type": "streamable-http",
"url": "https://mcp.genesisre.io/mcp"
}
}
}Cursor / Windsurf / Codex / Replit
Use the same MCP URL and keep inputs non-confidential.
MCP_SERVER_NAME=proofrelay MCP_URL=https://mcp.genesisre.io/mcp ALLOWED_TOOLS=proofrelay.get_verifier_status,proofrelay.recommend_checkpoint,proofrelay.verify_bundle,proofrelay.normalize_payment_proof,proofrelay.build_bundle_draft,proofrelay.describe_stripe_entitlement_flow,proofrelay.adapt_x402_payment_proof,proofrelay.plan_replay_rejection_test,proofrelay.wrap_mcp_tool_evidence,proofrelay.map_openapi_operation_evidence,proofrelay.generate_paid_tool_receipt,proofrelay.scan_mcp_risk,proofrelay.describe_cli_sdk_helper,proofrelay.build_human_approval_receipt,proofrelay.build_audit_pack_manifest,proofrelay.summarize_agent_action_log,proofrelay.review_vendor_risk_profile,proofrelay.build_title_production_evidence,proofrelay.build_closing_proof_pack,proofrelay.review_wire_payoff_change,proofrelay.map_lender_condition_evidence,proofrelay.compute_readiness_signal,proofrelay.adapt_agent_identity_evidence,proofrelay.build_registry_entry,proofrelay.issue_conformance_badge,proofrelay.verify_signed_attestation
Invisible checkpoint helper
Use pass/fail/review status locally before exposing full bundle details.
python3 scripts/revenue/proofrelay_invisible_layer.py --demo # In code: checkpoint_and_verify(service, action_class, tool_name, request, response) # Returns: pass | fail | needs_review | skipped
Health and server card
Use these endpoints for Smithery and CI smoke checks.
curl -fsS https://mcp.genesisre.io/health curl -fsS https://mcp.genesisre.io/.well-known/mcp/server-card.json curl -fsS https://mcp.genesisre.io/.well-known/mcp.json
Hermes builder control proof
Use the targeted Hermes page before community promotion.
Open https://genesisre.io/proofrelay/hermes Connect https://mcp.genesisre.io/mcp Start with proofrelay.get_verifier_status, proofrelay.recommend_checkpoint, proofrelay.verify_bundle
Example evidence calls
Replace placeholders with locally computed hashes. Never send raw credentials, prompts, customer files, wire instructions, or source data.
Wrap a paid MCP tool result
proofrelay.wrap_mcp_tool_evidence({
tool_evidence: {
tool_name: "vendor.lookup",
request_hash: "<sha256>",
response_hash: "<sha256>"
}
})Prepare governance audit evidence
proofrelay.build_human_approval_receipt({
approval: {
approver_role: "ops_approver",
approver_hash: "<sha256>",
decision: "approved",
subject_hash: "<sha256>"
}
})Build real-estate readiness evidence
proofrelay.compute_readiness_signal({
readiness: {
workflow_hash: "<sha256>",
target_milestone: "closing",
title_evidence_hash: "<sha256>"
}
})Operational guardrails
- • Call get_verifier_status before submitting bundles.
- • Submit only minimized, non-confidential evidence bundles.
- • Do not send credentials, raw prompts, customer files, or private logs.
- • Do not expect public MCP calls to process payments, redeem tokens, settle x402 charges, or custody evidence.
- • Use recommend_checkpoint to decide when paid actions need receipts.
- • Use governance and real-estate helpers as unsigned evidence planners only.
- • Verify signed attestations with public keys only; never submit private keys.
- • Use the paid intake path when a workflow needs retention or team support.