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.
git clone --depth 1 https://github.com/RikiGomes/woodpecker-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/rikigomes/woodpecker-mcp/woodpecker-mcp)<a href="https://agentmods.dev/mcp/rikigomes/woodpecker-mcp/woodpecker-mcp"><img src="https://agentmods.dev/badge/mcp/rikigomes/woodpecker-mcp/woodpecker-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/rikigomes/woodpecker-mcp/woodpecker-mcp"><img src="https://agentmods.dev/badge/mcp/rikigomes/woodpecker-mcp/woodpecker-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
woodpecker-mcp 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 2mo 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
{ "woodpecker-mcp": { "command": "npx", "args": [ "-y", "woodpecker-mcp" ] } }
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.
- 2mo ago First seen · 9 lines scan A 2b22b2d39f82
woodpecker-mcp is an MCP server published in the GitHub repository RikiGomes/woodpecker-mcp (0 stars, last pushed 5d 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-09-01.
Other mcp servers, from other repositories
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.
woodpecker-ci-mcp
Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons. Runs locally from the @ni-c/woodpecker-ci-mcp npm package. Needs 7 environment variables to run.
mcp-zuul
MCP server for Zuul CI — build failure analysis, log search, pipeline status, and job configuration. Runs locally from the mcp-zuul Python package. Needs 7 environment variables to run.
healthchecksio
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io. Remote server at healthchecksio.usefulapi.io.
codemagic
Trigger and inspect Codemagic CI builds, apps and artifacts. Remote server at codemagic.usefulapi.io.
depot
Inspect Depot builds, CI runs, job logs and Actions runners; retry or cancel CI runs. Remote server at depot.usefulapi.io.