gha-doctor
OCI · GHCR.IO/LINNEA-BAKSHI/GHA-DOCTOR:0.66.0
Diagnose GitHub Actions CI: lint, flaky tests, wasted minutes, health score. Read-only MCP tools.
Available components
Last scanned (21 hours ago)
Scores higher than 93% of OCI servers
Category CI/CD and DevOps
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 56 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1103 tokens (~157/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed oci/ghcr.io/linnea-bakshi/gha-doctor:0.66.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_repo ~266
Full CI health report for a GitHub repository: static workflow lint, run-history analysis (success/failure rates, flaky jobs, retry waste, superseded PR runs, queue times, duration trends, zombie crons, PR feedback time), cache and artifact checkups, a 0-100 health score, and a ranked, dollar-quantified top-wins list. Makes ~100+ GitHub API calls and typically takes 10-30 seconds. Optionally set flaky_logs to also read N flaky-failure job logs and name the flaky tests (needs a token), or cache_logs to measure the real cache hit rate from N job logs.
| Name | Type | Req | Description |
|---|---|---|---|
| cache_logs | integer | – | Sample N job logs to measure the real cache hit/miss rate (1 API request per log; needs a token) |
| flaky_logs | integer | – | Read N flaky-failure job logs to name the flaky tests (1 API request per log; needs a token) |
| repo | string | yes | Repository as owner/name, e.g. cli/cli |
| runs | integer | – | Number of recent runs to sample (default 100) |
| workflow | string | – | Scope the history analysis to one workflow (file name like ci.yml, or display name); no health score in scoped mode |
No output schema declared.
No examples provided.
explain_rule ~63
Print the full documentation for one lint rule: what it flags, why it matters, how to fix it, and how to suppress it. Rule IDs look like D001; every finding cites one.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | Rule ID, e.g. D001 |
No output schema declared.
No examples provided.
lint_repo ~125
Static lint of GitHub Actions workflows and action manifests only (no run history, fast): 21 rules covering missing timeouts, no concurrency cancellation, dead action versions, retired runner labels, deprecated workflow commands, unguarded crons, and more. Pass repo to lint any GitHub repository via the API (no clone needed), or dir for a local checkout (offline). Defaults to the current directory.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Local repository directory to lint (default ".") |
| repo | string | – | Repository as owner/name to lint remotely (mutually exclusive with dir) |
No output schema declared.
No examples provided.
org_overview ~109
Fleet triage across an organization's (or user's) most recently pushed repositories: per-repo run counts, failure rates, median duration, compute minutes, last-run age, and fleet-wide zombie crons (scheduled workflows failing on repeat), one API call per repo. Useful for finding which repository's CI to look at first.
| Name | Type | Req | Description |
|---|---|---|---|
| max_repos | integer | – | Max repositories to scan, most recently pushed first (default 20) |
| org | string | yes | GitHub organization or user login |
No output schema declared.
No examples provided.
pr_deep_dive ~145
Diagnose a pull request's CI: every workflow run on the PR's head commit, how long the PR waited for a verdict, re-run smells, and a full deep dive into the latest failed run — failing job and step, named failing tests (30+ frameworks recognized), and the failing step's log tail. The natural first call when someone asks why CI is failing or slow on their PR.
| Name | Type | Req | Description |
|---|---|---|---|
| log_tail | integer | – | Lines of the failing step's log to include per failed job (default 20, 0 = off; needs a token) |
| pr | integer | yes | Pull request number |
| repo | string | yes | Repository as owner/name |
No output schema declared.
No examples provided.
preview_fixes ~111
Preview the exact unified diff that gha-doctor --fix would apply for auto-fixable findings (10 of 21 rules), without writing anything. Pass repo for any GitHub repository (no clone needed) or dir for a local checkout. To actually apply fixes, run `gha-doctor --fix` in the repository — this MCP server never writes.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Local repository directory (default ".") |
| repo | string | – | Repository as owner/name (mutually exclusive with dir) |
No output schema declared.
No examples provided.
run_deep_dive ~155
Deep-dive one workflow run: why was it slow, or why did it fail? Job waterfall (queue vs execution), every job and step compared against the workflow's own recent medians, named step regressions; failed runs lead with the failing job and step, name the failing tests (30+ test frameworks recognized), and inline the failing step's log tail (needs a token).
| Name | Type | Req | Description |
|---|---|---|---|
| log_tail | integer | – | Lines of the failing step's log to include per failed job (default 20, 0 = off; needs a token) |
| repo | string | yes | Repository as owner/name |
| run | string | – | Run ID, full run URL, or "latest" (default "latest") |
No output schema declared.
No examples provided.
How do I install the gha-doctor MCP server?
gha-doctor runs locally as a container image, launched with docker run --rm -i -e GITHUB_TOKEN ghcr.io/linnea-bakshi/gha-doctor:0.66.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/linnea-bakshi/gha-doctor:0.66.0
claude mcp add linnea-bakshi-gha-doctor -- docker run --rm -i -e GITHUB_TOKEN ghcr.io/linnea-bakshi/gha-doctor:0.66.0
This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the gha-doctor MCP server?
gha-doctor is an MCP server listed in the public MCP registry as io.github.linnea-bakshi/gha-doctor. Diagnose GitHub Actions CI: lint, flaky tests, wasted minutes, health score. Read-only MCP tools. This page covers its container image (ghcr.io/linnea-bakshi/gha-doctor:0.66.0).
Is the gha-doctor MCP server safe to use?
gha-doctor scores 55 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the gha-doctor MCP server expose?
gha-doctor exposes 7 tools: analyze_repo, lint_repo, preview_fixes, run_deep_dive, pr_deep_dive, and 2 more. Their descriptions and schemas cost roughly 974 tokens of context every time the server is loaded.
Is the gha-doctor MCP server still maintained?
gha-doctor is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the gha-doctor MCP server under?
gha-doctor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.