Start a persisted conformance run
Grades the saved server against the protocol, apps, and tasks suites and returns 202 with a run id. The target comes from the saved server the path names: a body cannot supply a URL. OAuth is not startable here. Poll the run detail for the verdict. Status, outcome, and score are three different answers.
By default the run uses the server’s saved conformance settings: the checks they select, their tool inputs and their run time budget. The receipt’s settingsSource says what applied: saved, or defaults when the server has nothing saved. settings: "none" runs every check with no tool inputs. With saved settings, the start first checks which MCP protocol version the server speaks and leaves out any suite with no saved checks for that version, as the app does. A retry with the same idempotency key returns the run that key started, with its original suites and settings. A run still going at its budget ends with its unfinished suites incomplete.
On hosted MCPJam, a user’s starts past 30 in 10 minutes can be refused with 429 and Retry-After. A server that is restarting also answers 429 with Retry-After, with details.reason SERVER_DRAINING.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Headers
The launching process's own DECLARED identity, as compact JSON: {"kind":"cli"|"mcp"|"github_action","client":"…","version":"…"}. Stored on the run as launcher and used only as a display label: source stays api and the audit trail reads the platform-minted attribution instead.
A malformed value, or a kind outside the three above, is DROPPED rather than rejected, so a label never fails a launch. Max 512 bytes.
Path Parameters
Body
Response
The run was accepted and is executing.

