Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/tsviz/github-mcp-server-devops/actions-pulsegit clone --depth 1 https://github.com/tsviz/github-mcp-server-devopsGrade A, and why
actions-pulse scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"actions-pulse": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tsviz/actions-pulse:v2.3.0"
],
"env": {
"GITHUB_TOKEN": "",
"GITHUB_ORG": "",
"GITHUB_ENTERPRISE_SLUG": "",
"DEFAULT_REPO_FILTER": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 17 lines scan A 6381f82c2d65
actions-pulse is an MCP server published in the GitHub repository tsviz/github-mcp-server-devops (3 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
buildkite-mcp-server
MCP server "buildkite-mcp-server" as configured in buildkite/buildkite-mcp-server. Runs in Docker (ghcr.io/buildkite/buildkite-mcp-server:0.7.0). Needs 1 environment variable to run.
teamcity
MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants. Runs locally from the @daghis/teamcity-mcp npm package. Needs 3 environment variables to run.
waitbus
Workstation-local event bus and blocking wait/emit primitive: let any agent or script wait on or emit CI, pytest, Docker, and filesystem events without polling. GitHub Actions is source #1. Runs locally from the waitbus Python package.
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
gha-doctor
MCP server "gha-doctor" as configured in linnea-bakshi/gha-doctor. Runs in Docker (ghcr.io/linnea-bakshi/gha-doctor:0.61.0). Needs 1 environment variable to run.
blacksmith
MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests. Runs locally from the blacksmith-mcp npm package. Needs 2 environment variables to run.