Check GitHub Actions workflows live: retired actions, bad inputs, injection. Pin actions to SHAs.
MCP Score How we grade
From what our daily checks can see without credentials, last checked 21 Nov 2026.
| Reliability Answered 3 of 3 daily checks. |
30 / 30 |
| Speed Typical response 261 ms. |
12 / 20 |
| Tool docs 2 of 2 tools have a full description; 6 of 6 inputs have a description. |
25 / 25 |
| Stability No tool rewrites in 30 days. |
15 / 15 |
| Listing Complete registry listing. |
10 / 10 |
How to raise the grade
- Answer initialize faster: under 150 ms earns full Speed points (yours: 261 ms).
Connect Remote server
claude mcp add --transport http tack https://tack.clawhard.com/mcp
{
"mcpServers": {
"tack": {
"url": "https://tack.clawhard.com/mcp"
}
}
}
{
"servers": {
"tack": {
"type": "http",
"url": "https://tack.clawhard.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://tack.clawhard.com/mcp
Tools 2 found in our last check
tack_check_workflowUse 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…
tack_resolve_actionsUse 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",…
Details
| Endpoint | https://tack.clawhard.com/mcp (Streamable HTTP) |
| First published | 19 Nov 2026 |
| Last updated | 19 Nov 2026 |
| Registry name | com.clawhard/tack |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
