Tack

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
100%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,150Tokens (definiciones de herramientas)
~1.7 KBTamaño de respuesta típico
Impacto moderado en la atención (0.90% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

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

Puntos de conexión remotos

https://tack.clawhard.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (2)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢tack_check_workflow(workflow, upgrade, live, kind)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "workflow": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200000,
      "description": "The YAML text of a workflow file (.github/workflows/<name>.yml) or of an action.yml / action.yaml."
    },
    "upgrade": {
      "type": "boolean",
      "description": "Pin every action to its latest release instead of the version the file uses. Default false (retired or missing refs are moved to the latest release either way)."
    },
    "live": {
      "type": "boolean",
      "description": "Resolve actions, inputs and runner labels on github.com. Default true; false = offline YAML and syntax checks only."
    },
    "kind": {
      "type": "string",
      "enum": [
        "auto",
        "workflow",
        "action"
      ],
      "description": "auto (default) detects a workflow (jobs:) or an action metadata file (runs:)."
    }
  },
  "required": [
    "workflow"
  ]
}
🟢tack_resolve_actions(actions, upgrade)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "actions": {
      "type": "array",
      "minItems": 1,
      "maxItems": 30,
      "items": {
        "type": "string",
        "minLength": 3,
        "maxLength": 300
      },
      "description": "Action references: \"owner/repo\" (latest release), \"owner/repo@v4\", \"owner/repo/path@ref\", or a full uses: line."
    },
    "upgrade": {
      "type": "boolean",
      "description": "For references with a ref, return the pinned line for the latest release instead. Default false."
    }
  },
  "required": [
    "actions"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada2 herramientas