Skip to main content
Glama

Tack

Server Details

Check GitHub Actions workflows live: retired actions, bad inputs, injection. Pin actions to SHAs.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools operate at clearly different granularities: tack_check_workflow validates a whole workflow file, while tack_resolve_actions resolves individual `uses:` references. Each description explicitly names the other as the fallback for the other's use case, eliminating selection ambiguity.

Naming Consistency5/5

Both names use the same `tack_` server prefix followed by a verb_noun pattern (check_workflow, resolve_actions). There are no mixed conventions or stylistic outliers.

Tool Count3/5

Two tools is thin for a toolset, though each is deliberately heavy and the domain (workflow validation + action ref resolution) is narrow. There is no obviously missing third entry point, but the surface offers only two ways in.

Completeness4/5

The pair covers the core lifecycle: parse/validate a workflow, resolve every action ref, and emit a fully SHA-pinned file. Minor gaps remain (no multi-file/bulk workflow checking, no applying arbitrary fixes beyond pinning, no private-repo or settings inspection), but these are documented exclusions rather than dead ends.

Available Tools

2 tools
tack_check_workflowCheck a GitHub Actions workflow and pin every action to a commit SHA (live)A
Read-onlyIdempotent
Inspect

Use when the user asks to write, review, fix or harden a GitHub Actions workflow (.github/workflows/*.yml) or a composite action.yml, or when a workflow was just written or edited and is about to be committed (signals: "write a CI workflow", "why does my workflow fail", "Invalid workflow file", "Unexpected input", "pin actions to SHA", "is actions/checkout@v4 still current", "Node 20 deprecated", "upload-artifact v3", "runs-on ubuntu-20.04", "script injection", "pull_request_target"). Parses the YAML (errors with line and column, duplicate keys, anchors), checks the structure against GitHub's workflow syntax as documented on 2026-11-19 (including recent keys such as schedule timezone, cache-mode, background, wait, wait-all, cancel, parallel and $/ self-repository references), then resolves every uses: reference live on github.com: whether the repository, tag, branch or commit exists, which release a SHA is, the latest release, retired versions that make a job fail (upload/download-artifact v3 and older, actions/cache v1-v2 and old exact pins), runs.using node20-or-older runtimes, with: inputs the action does not declare (with a did-you-mean), missing required inputs, reusable-workflow inputs, and pinned-SHA comments that name the wrong version. Also flags retired runner labels (live runner-images list), script injection through ${{ github.event... }} in run:, pull_request_target checkouts of PR code, and a missing permissions key. Returns each finding with line, path, fix and doc link, per-action resolution, fix_message, and pinned_workflow: the same file with every action pinned to its full commit SHA and a # version comment (retired or missing refs move to the latest release; upgrade:true moves all). Example: {"workflow":"on: push\njobs:\n test:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - uses: actions/setup-node@v4\n with:\n node_version: 20"}. Does not run the workflow, evaluate expressions or see private repositories, secrets or repository settings. Up to 200000 characters.

Inputs: workflow (required), kind, live, upgrade.

tack_resolve_actionsLook up GitHub Actions: latest release, commit SHA, runtime and inputs (live)A
Read-onlyIdempotent
Inspect

Use when a uses: line for a GitHub Action is about to be written and its current version, commit SHA or inputs are needed, or the user asks what the latest version of an action is, what SHA a tag points to, or whether an action or tag exists (signals: "latest actions/checkout", "pin setup-node to a SHA", "what inputs does this action take", "does v9 exist", "which version is this SHA"). Takes owner/repo (latest release), owner/repo@ref or owner/repo/path@ref, reads the tags and branches live from github.com and the action.yml at that commit, and returns per action: exists or not, the commit SHA, the release a SHA or major tag points to, the latest release and major tag, runs.using (flags node20 and older, which GitHub stopped shipping on 2026-09-23), retired versions that fail jobs, the declared inputs, and a ready-to-paste line: uses: owner/repo@<40-char sha> # vX.Y.Z. Example: {"actions":["actions/checkout","actions/setup-node@v4","docker/build-push-action@v6"]}. Up to 30 per call. Public github.com repositories only; for a whole workflow file use tack_check_workflow.

Inputs: actions (required), upgrade.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Audits GitHub Actions workflow files for supply-chain risks like script injection, leaked tokens, unpinned actions, and broad permissions.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Scans 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.
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      3
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables offline auditing of GitHub Actions workflows through MCP, surfacing security and correctness findings with exact file/line locations and fixes, explaining cron schedules, visualizing job dependencies, reviewing token permissions, planning commit-SHA pins, and previewing safe patches proven by re-linting.
      7
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources