For server implementers
Conformance
The rules a conforming server keeps, and the fixtures to test it with.
A server conforms when it keeps the five rules of the specification §6, offers the required tools with the contracts in tool contracts, refuses what §2 says to refuse, and reports what it offers in describe.
Fixtures
Each fixture is a folder with one PROCESS.md. The first ten were written by independent reviewers (research) and use the core only. A conforming server publishes all ten. The last two exercise the profiles; a server publishes each one only if it offers that profile.
| Process | What it exercises |
|---|---|
| blog-publication | wait_until on an input date, approval with on_reject |
| contract-review | A person task, two approvals, a person path, file evidence |
| customer-offboarding | Route lists, wait_until, wait_for with timeout |
| employee-onboarding | person paths, approval with on_reject |
| expense-reimbursement | initiator, a person path, file evidence |
| incident-postmortem | person paths, repeated rework through on_reject |
| invoice-approval | A route list, a person path |
| major-incident-response | Simultaneous work attempted in core only: the case that led to parallel |
| supplier-rfp | File evidence, approval with on_reject |
| support-escalation | A route list, approval with on_reject |
| major-incident | The parallel profile: fork, join, a person path |
| vendor-check | The check profile on a route list with file evidence; requires |
Running it
Today the suite runs inside the reference server's own tests, which publish every fixture and replay the review traces over a real MCP client. A portable runner that takes any server's URL and a token is planned; until it exists, an implementer can use the fixtures and the traces in the review documents to test by hand.