Ci Guard MCP server
io.github.carelessdept/ci-guard-mcp·v0.1.0Local-first static repository security and configuration drift auditor (CLI, GitHub Action & MCP).
0 stars51 downloads/wk
Reviews
Write oneNobody has reviewed Ci Guard yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Ci Guard tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it
- Code scan28 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Ci Guard compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 1,119 Developer tools servers
- Downloads a week
- 51
- more than 38% of 436 Developer tools servers with a package
Install Ci Guard in Claude Code, Cursor or VS Code
Runs npx -y ci-guard-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add ci-guard-mcp -- npx -y ci-guard-mcp
What the publisher says
From the Ci Guard repository's README, as published. We do not edit it. Read it on GitHub
ci-guard-mcp
One local audit engine. A CLI, a GitHub Action, and four MCP tools.
Catch risky GitHub workflows, undocumented environment variables, possible credentials, and conflicting dependency configuration before merging. Audits are deterministic, read-only, and run without sending source code to a service. Two runtime dependencies: yaml and ignore.
Run locally
Requires Node.js 20 or later. Git is required for index scans and tracked-file selection.
# Run directly with npx:
npx ci-guard-mcp scan . --fail-on warn
npx ci-guard-mcp scan . --sandbox
npx ci-guard-mcp scan . --no-git
npx ci-guard-mcp scan . --format json
npx ci-guard-mcp scan . --format sarif > findings.sarif
npx ci-guard-mcp scan . --auditor workflows --auditor lockfile
npx ci-guard-mcp scan . --auditor secrets --staged
npx ci-guard-mcp scan . --auditor secrets --include-ignored
# Or from a local source checkout:
npm ci --ignore-scripts
npm run build
node dist/cli.js scan .Exit codes: 0 below threshold, 1 findings at or above threshold, 2 invalid arguments, configuration or I/O failure. --fail-on error is the default; warn also fails on warnings. Informational findings never fail a scan. Output formats are text, json, sarif, and github. --root PATH is equivalent to the positional scan directory. --include-ignored audits tracked files even when they match .gitignore rules (for example, a .env committed before .gitignore was added). --help lists every flag.
Staged mode is intentionally limited to secrets: it reads entire changed index blobs, including renamed/added files, so unstaged edits cannot conceal a staged credential. It applies ignore rules from the index and skips deletions, symlinks and submodules. Other audits need the repository-wide context and cannot be combined with --staged.
GitHub Action
After this repository is published, use a reviewed full commit SHA in place of FULLCOMMITSHA:
name: Repository audit
on: [push, pull_request]
permissions:
contents: read
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
- uses: carelessdept/ci-guard-mcp@FULL_COMMIT_SHA
id: guard
with:
path: .
fail-on: warnInputs: path (default .), fail-on (error or warn, default error). Outputs: errors, warnings, findings as decimal counts. Outputs and the Markdown job summary are written before the finding threshold is evaluated. Findings become escaped workflow annotations; a failed audit exits the action with status 1. Operational failure exits 2 and does not claim complete counts.
This composite action installs its locked build dependencies with lifecycle scripts disabled into a runner-temp directory and runs the compiled CLI. It requires npm registry access, Bash, and a runner compatible with actions/setup-node@v4. The scanned repository's dependencies and scripts are never installed or executed. The self-audit workflow runs the local action and verifies its outputs. Run the CLI separately with --format sarif when uploading to a code-scanning service; the action itself does not upload reports or request write permissions.
MCP server
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Ci Guard: common questions
- Is Ci Guard MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Ci Guard safety report
- How do I install Ci Guard?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Ci Guard need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Ci Guard maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v0.1.0.
- What can I use instead of Ci Guard?
- Servers from other publishers that do the same job: Gk CLI MCP server, Grasp — Code Architecture & Dependency Analysis MCP server and zanadir MCP server.
- How does Ci Guard compare with other Developer tools MCP servers?
- safety score 89/100 (higher than 80% of 1,119 Developer tools servers); downloads a week 51 (more than 38% of 436 Developer tools servers with a package). Full comparison.
Alternatives to Ci Guard
Same job from other publishers: the closest match first, then the best rated.
Gk CLIThe GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.not reviewedEstablishedB- Grasp — Code Architecture & Dependency AnalysisCodebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.not reviewedGrowingC
- zanadirFind what a repository's CI is missing, and which security checks cannot fail the build.not reviewedGrowingB
- Pare GithubPare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.not reviewedGrowingA
- GitDiagramArchitecture diagrams, explanations and Mermaid source for public GitHub repositories.not reviewedEstablishedA