---
title: "List GitHub Checks repositories"
method: GET
path: "/organizations/{organizationId}/eval-check-repos"
tags: ["Evals"]
---

# List GitHub Checks repositories

`GET /organizations/{organizationId}/eval-check-repos`

The repositories in this organization whose pull requests run an eval suite, plus the repositories the MCPJam GitHub App can reach (the choices a connect has).

`available: false` means GitHub Checks is not enabled for this organization at all — connecting a repository will not help. `connectable: null` means the App could not be asked (GitHub unavailable, or no installation), which is different from an empty list meaning it reaches nothing; the already-connected list needs no GitHub call and is returned either way.

## Response `200`

Connected and connectable repositories.

- EvalCheckRepos
  - `organizationId` string, required
  - `available` boolean, required — Whether GitHub Checks is available for this organization at all. `false` and "available, nothing connected" are different situations, and only one of them is fixed by connecting a repository.
  - `items` EvalCheckRepo[], required — The repositories already connected.
    - `id` string, required
    - `repo` string, required — `owner/repo`, canonicalized by the platform.
    - `enabled` boolean, required
    - `suiteId` string, nullable, required — The eval suite this repository's pull requests run.
    - `projectId` string, nullable, required
    - `outagePolicy` 'fail_open' | 'fail_closed' | 'null', nullable, required — What the check reports when MCPJam cannot conclude. `null` is a REAL state — nobody chose a policy, because the repository was connected before the choice existed. The effective behaviour is `fail_open`, but reporting `fail_open` would say someone picked it.
    - `createdAt` number, nullable, required — Epoch milliseconds.
    - `updatedAt` number, nullable, required
  - `connectable` object[], nullable, required — The repositories the MCPJam GitHub App can reach — the choices a connect has. `null` means the question could not be ASKED: the lookup itself failed (GitHub unreachable, or the call errored); the connected `items` still stand, as they need no GitHub call. An EMPTY list means it was asked and came back with nothing, which covers two situations the platform does not distinguish: the App is installed but reaches no repository, and this deployment has no App installation at all. If a connect is failing against an empty list, check the installation before assuming a permissions problem.
    - `repo` string, 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.
- `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/ece7d99ceaf3/schema)