# io.github.CloudCorpRecords/flowcheck (oci · ghcr.io/cloudcorprecords/flowcheck)

Least-privilege auditor for GitHub Actions workflows: permissions, triggers, secrets.

- Trust score: 48/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/flowcheck`: 73/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-flowcheck/reneturcios-flowcheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-flowcheck/reneturcios-flowcheck)
- oci · `ghcr.io/cloudcorprecords/flowcheck`: 48/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-flowcheck/ghcr-io-cloudcorprecords-flowcheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-flowcheck/ghcr-io-cloudcorprecords-flowcheck)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/flowcheck`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 291 tokens (~145/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the io.github.CloudCorpRecords/flowcheck MCP server?

io.github.CloudCorpRecords/flowcheck runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/flowcheck:0.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-flowcheck -- docker run --rm -i ghcr.io/cloudcorprecords/flowcheck:0.1.2
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-flowcheck": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/flowcheck:0.1.2"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-flowcheck": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/flowcheck:0.1.2"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-flowcheck -- docker run --rm -i ghcr.io/cloudcorprecords/flowcheck:0.1.2
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-flowcheck": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/flowcheck:0.1.2"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-flowcheck:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/flowcheck:0.1.2"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-flowcheck": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/flowcheck:0.1.2"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-flowcheck": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/flowcheck:0.1.2"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 46, 0)

- [security regression] Provenance: unverified → fail

### 2026-10-30 (score 46, +1)

- [security regression] Provenance: fail → unverified

### 2026-10-28 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 44, +1)

- [functional] Package version: 0.1.1 → 0.1.2

### 2026-10-24 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 42, 0)

- [functional] Package version: 0.1.0 → 0.1.1

## MCP tools (2)

### `audit_workflows` (~160 tokens)

Audit GitHub workflow files under a repo path for least-privilege problems: missing or write-all permissions, per-job grants broader than the job's steps need, pull_request_target or workflow_run or issue_comment triggers combined with a checkout of the PR head, secrets in fork-reachable contexts, secrets: inherit to reusable workflows, self-hosted runners on PR triggers, cache poisoning surface, whole-workspace artifact uploads, missing timeouts, and missing concurrency guards on deploy-shaped jobs. Returns a HARDENED, REVIEW, or EXPOSED verdict with file, job, and line evidence per finding, plus a hardened permissions plan per job.

Input parameters:

- `path` (string, required): Repo root, a .github/workflows directory, or a single workflow file

### `harden_plan` (~131 tokens)

Build the least-privilege hardening plan for workflows under a repo path without writing any files. For each job, infers the permissions its steps actually need (checkout is contents: read, release creation is contents: write, GHCR push is packages: write, PR comments are pull-requests: write, and so on) and returns a paste-ready permissions block per job plus a top-level union block, with notes where a grant is removed or a privileged trigger shape needs a human decision.

Input parameters:

- `path` (string, required): Repo root, a .github/workflows directory, or a single workflow file

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-flowcheck/ghcr-io-cloudcorprecords-flowcheck#diagnostics

## Score history

- 2026-11-05: 48
- 2026-11-04: 48
- 2026-11-03: 47
- 2026-11-02: 47
- 2026-11-01: 46
- 2026-10-31: 46
- 2026-10-30: 46
- 2026-10-29: 45
- 2026-10-28: 45
- 2026-10-27: 44
- 2026-10-26: 44
- 2026-10-25: 43
- 2026-10-24: 43
- 2026-10-23: 42
- 2026-10-22: 42

## Common questions

### What is the io.github.CloudCorpRecords/flowcheck MCP server?

io.github.CloudCorpRecords/flowcheck is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/flowcheck. Least-privilege auditor for GitHub Actions workflows: permissions, triggers, secrets. This page covers its container image (ghcr.io/cloudcorprecords/flowcheck).

### Is the io.github.CloudCorpRecords/flowcheck MCP server safe to use?

io.github.CloudCorpRecords/flowcheck scores 48 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/flowcheck MCP server expose?

io.github.CloudCorpRecords/flowcheck exposes 2 tools: audit_workflows, harden_plan. Their descriptions and schemas cost roughly 291 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/flowcheck MCP server still maintained?

io.github.CloudCorpRecords/flowcheck is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.CloudCorpRecords/flowcheck MCP server under?

io.github.CloudCorpRecords/flowcheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/flowcheck
- Repository: https://github.com/CloudCorpRecords/flowcheck
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-flowcheck/ghcr-io-cloudcorprecords-flowcheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-flowcheck/ghcr-io-cloudcorprecords-flowcheck.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-flowcheck/ghcr-io-cloudcorprecords-flowcheck