---
title: "Cancel an in-flight readiness run"
method: POST
path: "/projects/{projectId}/readiness-runs/{runId}/cancel"
tags: ["Directory readiness"]
---

# Cancel an in-flight readiness run

`POST /projects/{projectId}/readiness-runs/{runId}/cancel`

The executing node learns about this on its next heartbeat and aborts the run in flight, which matters more than the row's status: the thing being stopped is traffic to somebody else's server.

## Path parameters

- `projectId` string, required
- `runId` string, required

## Response `200`

The run was cancelled.

- object
  - `runId` string, required
  - `projectId` string, required
  - `status` 'cancelled', required

## Other responses

- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `409` — The run already reached a terminal status.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/a0fa11827b5e/schema)