gha-doctor runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 21 Sep 2026.
Diagnose GitHub Actions CI: lint, flaky tests, wasted minutes, health score. Read-only MCP tools.
What the code does
We read the source, 11 h ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
const res = spawnSync(bin, process.argv.slice(2), { stdio: 'inherit' });
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
path := filepath.Join(wfDir, name)
const res = spawnSync(bin, process.argv.slice(2), { stdio: 'inherit' });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch gha-doctor and you get told the day something new turns up.
Alternatives to gha-doctor
same job, measured the same wayFree MCP server: compute a GitHub repo maintenance/abandonment health score from live data.
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD.
Real-time GitHub Actions observability: DORA Metrics, Cost Analysis, CI/CD Health dashboards.
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
Diagnose proxy misconfigurations that break AI coding tools (Cursor, VS Code, Windsurf)
Local read-only MCP tools for Git repository archaeology, churn, hotspots, and hygiene. Tools...
A cited wiki of your GitHub repo: search, read pages, find symbols and ask, with line citations.
Monitor GitHub repo health, DORA metrics and CI signals from your AI assistant.
gha-doctor — questions
Answers built from our own checks of this server.