Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GitHub CI/CD MCP Server

NPM · @KINUS/GITHUB-CICD-MCP

GitHub CI/CD MCP server with 70 tools for repos, PRs, Actions, deployments, billing, and more.

0 Trust /100

Last scanned (8 hours ago)

Scores higher than 0% of npm servers

Category CI/CD and DevOps

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security73
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4500 tokens (~64/item across 70 items; 70 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "github_merge_pull_request" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 71 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Security disclosure: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 82 functional
  • 13 Oct 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 19 Oct 2026 · Analysed npm/@kinus/github-cicd-mcp@1.2.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 4 findings
ID CVE Severity Vector Fix available
GHSA-v5rq-49vh-5v5c CVE-2026-102829 critical yes
GHSA-858h-whjf-mvg5 CVE-2026-102827 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-g4wm-2vf7-vfgr CVE-2026-102826 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-x6jw-m9v5-85vh CVE-2026-102828 critical yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 116 packages
Packages resolved 116
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 70 exposed · ~4,414 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
github_list_deployments ~69

List deployments for a repository (CD history).

NameTypeReqDescription
environmentstring–Filter by environment name
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name

No output schema declared.

No examples provided.

github_list_environments ~40

List deployment environments and protection rules.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
repostringyesRepository name

No output schema declared.

No examples provided.

github_list_issue_comments ~64

List comments on an issue or PR.

NameTypeReqDescription
issue_numbernumberyes–
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name

No output schema declared.

No examples provided.

github_list_issues ~82

List issues (excludes pull requests unless filtered).

NameTypeReqDescription
labelsstring–Comma-separated label names
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name
statestring–open | closed | all

No output schema declared.

No examples provided.

github_list_pull_request_files ~50

List files changed in a pull request.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
pull_numbernumberyes–
repostringyesRepository name

No output schema declared.

No examples provided.

github_list_pull_requests ~70

List pull requests for a repository.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name
statestring–open | closed | all (default open)

No output schema declared.

No examples provided.

github_list_releases ~54

List releases for a repository.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name

No output schema declared.

No examples provided.

github_list_repositories ~69

List repositories for a user or organization.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
typestring–For orgs: all | public | private | forks | sources | member

No output schema declared.

No examples provided.

github_list_tags ~54

List git tags in a repository.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name

No output schema declared.

No examples provided.

github_list_teams ~44

List teams in an organization (for CI/CD access planning).

NameTypeReqDescription
orgstringyes–
per_pagenumber–Results per page (max 100)

No output schema declared.

No examples provided.

github_list_webhooks ~53

List repository webhooks.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name

No output schema declared.

No examples provided.

github_list_workflow_jobs ~53

List jobs for a workflow run (steps, conclusions).

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
repostringyesRepository name
run_idnumberyes–

No output schema declared.

No examples provided.

github_list_workflow_run_artifacts ~53

List CI build artifacts for a workflow run.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
repostringyesRepository name
run_idnumberyes–

No output schema declared.

No examples provided.

github_list_workflow_runs ~99

List workflow runs (filter by workflow id, branch, or status).

NameTypeReqDescription
branchstring––
ownerstringyesRepository owner (user or org login)
per_pagenumber–Results per page (max 100)
repostringyesRepository name
statusstring–queued | in_progress | completed | failure | success | etc.
workflow_idnumber–Workflow ID

No output schema declared.

No examples provided.

github_list_workflows ~42

List GitHub Actions workflows in a repository.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
repostringyesRepository name

No output schema declared.

No examples provided.

github_merge_pull_request ~92

Merge a pull request when checks pass (squash, merge, or rebase).

NameTypeReqDescription
commit_messagestring––
commit_titlestring––
merge_methodstring–merge | squash | rebase (default squash)
ownerstringyesRepository owner (user or org login)
pull_numbernumberyes–
repostringyesRepository name

No output schema declared.

No examples provided.

github_rerun_workflow ~52

Re-run a failed or cancelled workflow run.

NameTypeReqDescription
ownerstringyesRepository owner (user or org login)
repostringyesRepository name
run_idnumberyes–

No output schema declared.

No examples provided.

github_update_branch_protection ~157

Update branch protection (require PR reviews, status checks, admins).

NameTypeReqDescription
allow_deletionsboolean––
allow_force_pushesboolean––
branchstringyes–
enforce_adminsboolean––
ownerstringyesRepository owner (user or org login)
repostringyesRepository name
required_pull_request_reviewsstring–JSON: { "required_approving_review_count": 1 }
required_status_checksstring–JSON: { "strict": true, "contexts": ["ci/build"] }
restrictionsstring–JSON: { "users": [], "teams": [], "apps": [] } or null to disable

No output schema declared.

No examples provided.

github_update_issue ~92

Update issue title, body, state, or labels.

NameTypeReqDescription
bodystring––
issue_numbernumberyes–
labelsstring–JSON array of label names (replaces all labels)
ownerstringyesRepository owner (user or org login)
repostringyesRepository name
statestring–open | closed
titlestring––

No output schema declared.

No examples provided.

github_update_pull_request ~78

Update PR title, body, or state (open/closed).

NameTypeReqDescription
bodystring––
ownerstringyesRepository owner (user or org login)
pull_numbernumberyes–
repostringyesRepository name
statestring–open | closed
titlestring––

No output schema declared.

No examples provided.

Install

How do I install the GitHub CI/CD MCP Server server?

GitHub CI/CD MCP Server runs locally as an npm package, launched with npx -y @kinus/github-cicd-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @kinus/github-cicd-mcp

# add to Claude Code
claude mcp add devstephenke-sys-github-cicd -- npx -y @kinus/github-cicd-mcp
Common questions

What is the GitHub CI/CD MCP Server server?

GitHub CI/CD MCP Server is listed in the public MCP registry as io.github.devstephenke-sys/github-cicd. GitHub CI/CD MCP server with 70 tools for repos, PRs, Actions, deployments, billing, and more. This page covers its npm package (@kinus/github-cicd-mcp).

What tools does the GitHub CI/CD MCP Server server expose?

GitHub CI/CD MCP Server exposes 70 tools: github_get_authenticated_user, github_get_rate_limit, github_create_repository, github_get_repository, github_list_repositories, and 65 more. Their descriptions and schemas cost roughly 4,414 tokens of context every time the server is loaded.

Is the GitHub CI/CD MCP Server server still maintained?

GitHub CI/CD MCP Server is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the GitHub CI/CD MCP Server server under?

GitHub CI/CD MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.