What it does
It compares check runs and commit statuses on a pull request's head commit with those on its base commit, and labels each check as introduced, pre-existing, external, fixed, passing, indeterminate or pending. Hosted deploy checks, such as Vercel, Netlify and Cloudflare, and checks waiting for maintainer approval are classed as external before any base comparison. A failure with no base evidence is marked indeterminate, and a check whose completed runs disagree on the same commit is flagged as flaky.
It suits cases where a pull request shows many failing checks and the author needs to see which failures the change caused. The CLI exits with code 1 when introduced failures exist and 0 otherwise, so it can serve as a CI gate or a triage script. The MCP server offers diff_pr_ci, which takes a repository and PR number, and diff_ci_runs, which takes a repository and head and base SHAs.
Running it needs no credentials for public repositories. The GITHUB_TOKEN environment variable is optional and raises the GitHub API rate limit. If the head commit has no check runs, for example because workflow approval is pending, the tool warns that CI has not run and does not classify those failures.
Limitations and requirements
Checks are matched by exact name, so a renamed check appears as a removal plus an addition. The base comparison uses the check evidence recorded for the PR's base commit, taken from the PR object. Failures with no usable base evidence remain unclassified (indeterminate). If CI has not run on the head commit, failures cannot be classified. Setting GITHUB_TOKEN is optional and only raises the API rate limit; no other credentials are needed for public repositories.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/cidiff
Base-vs-head CI differ: which PR failures are introduced, pre-existing, external, or fixed.
v0.1.2As shown on registry.modelcontextprotocol.io when we last read it