Conformance Suite (Beta)

Validate MCP behavior against fixed protocol checks and collect pass/fail artifacts.

Why this exists

App-level scenarios are not enough if protocol behavior drifts. Conformance runs verify MCP handshake and request handling so client integrations remain stable.

When to use this vs DIY script

Use FakeMCP conformance when you need repeatable profile checks and persisted reports. Use DIY scripts when you are testing one temporary client behavior without report tracking.

Built-in profiles

export BASE_URL="https://fakemcp.com"
export PROJECT_TOKEN="replace_me"
curl -sS "$BASE_URL/v1/conformance/profiles"

Current profiles:

• mcp_basic: initialize + invalid frame handling
• mcp_tooling: includes tool invocation checks

Execute a conformance run

curl -sS -X POST "$BASE_URL/v1/conformance/runs" \
  -H "Content-Type: application/json" \
  -H "X-Project-Token: $PROJECT_TOKEN" \
  -d '{
    "profile": "mcp_tooling"
  }'

Save returned id as CONFORMANCE_RUN_ID.

Retrieve report

curl -sS "$BASE_URL/v1/conformance/runs/${CONFORMANCE_RUN_ID}" \
  -H "X-Project-Token: $PROJECT_TOKEN"

Report contains:

• checks[]: pass/fail matrix with details
• summary: totals for passed/failed checks
• reportR2Key: artifact key when object storage is configured