woodpecker-ci-mcp-server
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
kruyvanna
Source: github_repo_search
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get_step_logsGet logs for a specific pipeline step. Useful for debugging individual step failures or examining step output.
approve_pipelineApprove and start a pipeline that is blocked waiting for approval (e.g. a pull request from a fork on a repository requiring approval).
cancel_pipelineCancel a running or pending pipeline. Useful for stopping a stuck or no-longer-needed pipeline.
create_pipelineTrigger a new manual pipeline run for a repository on a given branch. Use this to (re)start CI for a branch without pushing a new commit.
decline_pipelineDecline a pipeline that is blocked waiting for approval, preventing it from running.
get_pipeline_configGet the configuration files (.woodpecker.yml) used by a specific pipeline. Essential understanding pipeline setup. If required information is not provided, use the git command or any available tool to get more context about the current commit, the repository, or the author of the commit.
get_pipelineGet detailed information about a specific pipeline, including workflows, steps, and error details. If required information is not provided, use the git command or any available tool to get more context about the current commit, the repository, or the author of the commit.
list_pipelinesList pipelines for a repository with optional filtering. Returns pipeline metadata including status, commit info, and timing. If required information is not provided, use the git command or any available tool to get more context about the current commit, the repository, or the author of the commit.
restart_pipelineRestart a previously run pipeline, optionally overriding it into a deploy event. Useful for retrying a failed pipeline.
activate_repositoryActivate a repository in Woodpecker CI, enabling pipelines for it. Requires the repository's forge_remote_id. Use search_repository or list_repositories first to find the forge_remote_id of the repository to activate.
get_repository_by_idGet repository details by ID. Useful when you already have the repo ID from other operations and need repository context.
list_repositoriesList all repositories with optional filtering. Returns repository metadata including configuration, status, and access details. If required information is not provided, use the git command or any available tool to get more context about the current commit, the repository, or the author of the commit…
repair_repositoryRepair a repository's webhook configuration in the forge. Use this when pipelines stop triggering because the webhook is missing or misconfigured.
search_repositoryFind a repository by its full name (owner/repo format). Returns repository details including ID, URLs, and configuration. If required information is not provided, use the git command or any available tool to get more context about the current commit, the repository, or the author of the commit.
update_repositoryUpdate a repository's Woodpecker CI settings. Only the provided fields are changed; omitted fields are left as-is.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
Tool annotations
8/15 tools have annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
15/15 tools missing one or more hints — get_step_logs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); approve_pipeline (missing: openWorldHint); cancel_pipeline (missing: openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.18.0 (high), @modelcontextprotocol/sdk@1.18.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dependency freshness
1/5 production deps stale: ts-results@2022-05-22 (4.3y)
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/kruyvanna/woodpecker-ci-mcp-server)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check