Why this demo comes first
The paid MCP repository audit example shows the Accord lifecycle without requiring an Ergo node, Base RPC, x402 facilitator or real funds. That makes it the right starting point for developers who want to understand the protocol before adding rail-specific complexity.
It demonstrates the shape of a paid tool call, handler execution, verifier result and settlement record.
Run it locally
Clone the repository, enter examples/15-paid-mcp-repo-audit, install dependencies and run npm run dev. The expected lifecycle is Agreement -> mock payment -> MCP wrapper -> handler -> verifier -> Verification Receipt -> Settlement Receipt.
Treat this as a learning environment. It proves the flow, not production readiness.
What to inspect
Look for the agreement hash, the payment or mock rail state, the verifier decision and the final settlement receipt. Those are the protocol records that matter.
Once those are clear, teams can evaluate how their own verifier, buyer policy and rail assumptions should work.
FAQ
Does the demo use real funds?
No. It uses a mock rail.
Is it safe for production?
No. It is a local learning demo.
Open the demo source
Run the full lifecycle locally with mock settlement.