GitHub Actions Version Check
Server Details
Check the latest major version of GitHub Actions before writing a workflow (e.g. checkout@v3).
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The tools are related but still target different questions: check_action compares a specific `uses:` value against latest and reports majors behind, while latest_action only fetches the latest/major tag. Because check_action also exposes latest tag data, latest_action can feel like a subset, but the boundary is understandable.
Both names end in `_action` and are easy to read, but they do not follow the same verb_noun pattern: `check_action` uses a verb while `latest_action` uses an adjective. This is a minor deviation rather than a confusing convention mix.
The server has a narrow purpose, and two tools cleanly cover the two needed operations: fetch the latest release and compare a used version. There is no bloat or obviously missing third core operation.
The core single-action version-check lifecycle is covered: get latest version and compare a specified version. Minor gaps remain around batch-checking multiple actions or inspecting workflow files, but agents can work around those for the stated purpose.
Available Tools
2 toolscheck_actionCheck a workflow uses: lineBRead-onlyIdempotentInspect
Compare a uses: value (e.g. actions/checkout@v3) with the action's latest release: majors behind and the tag to use.
Inputs: uses (required). Returns: latest
latest_actionLatest version of a GitHub ActionBRead-onlyIdempotentInspect
Latest release tag and major tag (e.g. v6) of an action like actions/checkout.
Inputs: action (required). Returns: latest
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Check GitHub Actions workflows live: retired actions, bad inputs, injection. Pin actions to SHAs.
GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection.
Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.
Breaking changes between two versions: npm, PyPI, GitHub Actions, Helm, Terraform, crates.io, Go.
Related MCP Servers
- AlicenseAqualityDmaintenanceFetches the latest version numbers for popular GitHub Actions from simonw/actions-latest, allowing users to easily check and update workflow versions.122 PyPIGPL 3.0
- AlicenseAqualityCmaintenanceEnables reviewing GitHub Actions workflows for outdated actions, deprecated Node runtimes, retired runners, deprecated commands, and security risks, with file, line, and fix for each finding.31MIT
- FlicenseNot gradedqualityDmaintenanceAudits GitHub Actions workflow files for supply-chain risks like script injection, leaked tokens, unpinned actions, and broad permissions.-
- AlicenseAqualityCmaintenanceScans GitHub Actions workflow files for dangerous triggers, template injection, unpinned actions, excessive permissions, and secrets in shell commands before they are committed, exposing the checks as MCP tools for agents.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.