GitHub Actions Audit MCP Server

GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection. The github actions audit mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

Point any MCP-capable client (Claude Desktop, Cursor, n8n, Make, Zapier, custom agents) at this server, hand it a workflow YAML, and get back structured findings with:

• Severity — — critical / high / medium / low / info
• Affected job and step — — exact location of the problem
• Description — — why it matters, with the actual attack vector
• Remediation — — what to do about it
• Fix snippet — — YAML you can paste directly

Configuration

You will need one environment variable: GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by UnbearableDev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the github actions audit mcp server does with a few real requests.