Tack No account · live from github.com

GitHub Actions workflow check

Pin it down.

Paste a workflow. Tack checks it against GitHub's current syntax, looks up every action live (does the tag exist, is it retired, does it still run on Node 20, are the inputs real) and hands it back pinned to commit SHAs.

Try
Live, not remembered

Every uses: line, resolved.

Tack reads each action's tags and branches from github.com and its action.yml at the exact commit. A tag that never existed (actions/checkout@v9), a repo that doesn't, an input the action doesn't take (node_version instead of node-version): you see it before the run fails.

What breaks jobs

Retired and outdated.

upload-artifact and download-artifact v3, actions/cache v2 and old cache pins fail outright. Actions that declare node20 now run on Node 24 since GitHub removed Node 20 on 2026-09-23. Retired runner labels like ubuntu-20.04 never get a machine.

Safer by default

Pinned to a commit.

Tags can be moved to different code. Tack swaps each tag for the full commit SHA it points to, keeps a # version comment, flags SHA comments that name the wrong version, and points out script injection and pull_request_target checkouts.

Use with AI

Workflows your agent didn't make up.

Add the MCP server https://tack.clawhard.com/mcp (tools tack_check_workflow and tack_resolve_actions) to Claude, ChatGPT, Cursor or any MCP client, or call the JSON API at /openapi.json. Your coding agent checks the workflow it just wrote and commits the pinned version, instead of guessing which version of an action is current. It is also on the Clawhard MCP server at https://mcp.clawhard.com/mcp.

Use Tack with your AI

Add Tack to ChatGPT, Claude, Cursor or any assistant that supports MCP, then ask it to check a GitHub Actions workflow against current syntax and live action versions (retired versions, Node 20 runtimes, wrong inputs, script injection) and pin every action to a commit SHA. No key, no login.

https://tack.clawhard.com/mcp

Claude Code

claude mcp add --transport http clawhard-tack https://tack.clawhard.com/mcp

Claude (web and desktop)

Press Add to Claude, or open Customize → Connectors → Add custom connector, paste the URL and leave sign-in empty.

ChatGPT

Open Plugins → + → Add custom MCP server, paste the URL, choose No authentication, accept the warning, then Create as a plugin. Start a chat and type @ to use it.

More ways to connect

Codex

codex mcp add clawhard-tack --url https://tack.clawhard.com/mcp

Gemini CLI

gemini mcp add --transport http clawhard-tack https://tack.clawhard.com/mcp

Cursor, Windsurf and others (mcp.json)

{
  "mcpServers": {
    "clawhard-tack": { "url": "https://tack.clawhard.com/mcp" }
  }
}

VS Code (.vscode/mcp.json)

{
  "servers": {
    "clawhard-tack": { "type": "http", "url": "https://tack.clawhard.com/mcp" }
  }
}

No desktop app? Add to VS Code in the browser · VS Code Insiders · Add to Cursor in the browser

Other apps: Goose · LM Studio. Any MCP client works with the URL (Streamable HTTP, no headers).

Common questions

Tack checks a GitHub Actions workflow the way GitHub will read it, then looks up every action live on github.com: does the tag exist, which commit is it, is the version retired, does it still declare Node 20, are the with: inputs real. It returns each problem with its line and a copy of the workflow with every action pinned to a full commit SHA. No account.

How do I pin GitHub Actions to a commit SHA?

Replace each uses: owner/repo@v4 with the full 40-character commit SHA that tag points to, plus a comment with the version: uses: actions/checkout@<sha> # v4.2.2. Tack does this for a whole workflow at once, reading each SHA live from github.com, and keeps your formatting.

Why does my workflow fail with upload-artifact or cache errors?

GitHub retired actions/upload-artifact and download-artifact v3 and older (January 2025) and actions/cache v1 and v2 (March 2025). Jobs that use them fail. Tack flags them and pins the latest release instead.

What does the Node 20 deprecation mean for my workflow?

GitHub removed Node 20 from its runners on September 23, 2026. Actions that declare node20 (or node16, node12) now run on Node 24, which can break them. Tack reads each action's action.yml at the version you use and shows which release declares node24.

Why does GitHub say "Unexpected input"?

The step passes a with: key the action does not declare, often a near miss like node_version instead of node-version. GitHub only logs a warning and ignores it. Tack reads the action's real inputs and suggests the right name.

Can an AI coding agent use Tack?

Yes. Add the MCP server https://tack.clawhard.com/mcp (tools tack_check_workflow and tack_resolve_actions) or call the JSON API at /openapi.json. It is also on the Clawhard MCP server at https://mcp.clawhard.com/mcp.

For AI assistants and developers: llms.txt · API (OpenAPI) · MCP server · sitemap