# GSC Scanner (oci · ghcr.io/poliakarmai/gsc-scanner)

Local security scanner for AI agents: SAST, SCA, secrets, IaC; verifies exploit and fix.

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

## Components

- oci · `ghcr.io/poliakarmai/gsc-scanner`: 41/100 (this document), [markdown](https://verifymcp.io/servers/poliakarmai-gsc-scanner/ghcr-io-poliakarmai-gsc-scanner.md), [page](https://verifymcp.io/servers/poliakarmai-gsc-scanner/ghcr-io-poliakarmai-gsc-scanner)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/poliakarmai/gsc-scanner`
- Version: `v1`
- 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**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1368 tokens (~136/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 GSC Scanner MCP server?

GSC Scanner runs locally as a container image, launched with docker run --rm -i -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1 mcp. 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 poliakarmai-gsc-scanner -- docker run --rm -i -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1 mcp
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Cursor

```json
{
  "mcpServers": {
    "poliakarmai-gsc-scanner": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GSC_ALLOWED_ROOTS",
        "ghcr.io/poliakarmai/gsc-scanner:v1",
        "mcp"
      ]
    }
  }
}
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### VS Code

```json
{
  "servers": {
    "poliakarmai-gsc-scanner": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GSC_ALLOWED_ROOTS",
        "ghcr.io/poliakarmai/gsc-scanner:v1",
        "mcp"
      ]
    }
  }
}
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Codex

```bash
codex mcp add poliakarmai-gsc-scanner -- docker run --rm -i -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1 mcp
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "poliakarmai-gsc-scanner": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "GSC_ALLOWED_ROOTS",
        "ghcr.io/poliakarmai/gsc-scanner:v1",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Hermes

```yaml
mcp_servers:
  poliakarmai-gsc-scanner:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "GSC_ALLOWED_ROOTS", "ghcr.io/poliakarmai/gsc-scanner:v1", "mcp"]
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Netclaw

```json
{
  "McpServers": {
    "poliakarmai-gsc-scanner": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GSC_ALLOWED_ROOTS",
        "ghcr.io/poliakarmai/gsc-scanner:v1",
        "mcp"
      ]
    }
  }
}
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Other

```json
{
  "mcpServers": {
    "poliakarmai-gsc-scanner": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GSC_ALLOWED_ROOTS",
        "ghcr.io/poliakarmai/gsc-scanner:v1",
        "mcp"
      ]
    }
  }
}
```

This image reads GSC_ALLOWED_ROOTS. Set it in your client's env block for this server; docker run -e passes it through to the container.

## 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-05 (score 41, +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-11-03 (score 40, +1)

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

### 2026-11-01 (score 39, +1)

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

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

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

### 2026-10-27 (score 37, +1)

- [security regression] Stability: 0.03 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-26 (score 36, −1)

- [security regression] Stability: 0.00 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Tool coverage: 67% → 45%
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: pass → fail
- [functional] First check of Schema quality: unverified

### 2026-10-25 (score 37)

First indexed and scored.

## MCP tools (10)

### `scan_repo` (~82 tokens)

Run a GSC security scan on a local repository path and return a summary.

Input parameters:

- `profile` (string): scan profile (audit, developer-review, ci).
- `repo_path` (string, required): absolute or relative path to the repository to scan.
- `scan_mode` (string): quick (regex-only) | standard (LLM revalidate) | deep (chains).

### `list_findings` (~53 tokens)

List recent findings from the GSC database (fast, no scan).

Input parameters:

- `limit` (integer): max number of findings (default 20, max 100).
- `project` (string): optional project name filter.

Output parameters:

- `result`

### `verify_finding` (~198 tokens)

Re-run a finding's PoC in the sandbox and report whether the exploit still works.

Scans the repo (to reconstruct the finding), locates the PoC, executes it in the
isolated sandbox and returns the result. Read-only w.r.t. the host system.

Response keys: ``verify_status`` is the verdict ("verified" |
"not_reproducible" | "unverified" | "unavailable" | "refused" |
"inconclusive"); ``status`` is the documented legacy alias. When the scan hit
its budget (``scan_status: "partial"``) the verdict is forced to
\``"inconclusive"``: a finding that was not re-detected in a partial scan is
missing from the scan, not from the repo (``error_code: "TRUNCATED"``).

Input parameters:

- `finding_key` (string, required)
- `repo_path` (string, required)

### `verify_fix` (~137 tokens)

Did the fix remove the finding? ``fixed`` | ``still_vulnerable`` | ``inconclusive``.

Re-scans the current tree (content-cached) and reports whether the finding is
still detected. ``fixed`` = rescan evidence only: the detector no longer
fires, which is NOT exploit-level proof (GSC-003) — ``verify_finding`` runs
the PoC for that. An unknown key is ``error_code: "NOT_FOUND"``: a key that
was never seen here cannot be called fixed.

Input parameters:

- `finding_key` (string, required)
- `repo_path` (string, required)

### `get_finding` (~170 tokens)

Return the full detail of a single finding identified by its finding_key.

Scans the repo (to reconstruct the finding), locates the matching finding by
its stable key and returns the complete record: rule, severity, location,
detail, fix, references and revalidation signals. Read-only.

Input parameters:

- `finding_key` (string, required)
- `project` (string): project name to scope the lookup (the name ``scan_repo`` saved the findings under — the repo directory name). The key is rule+file+snippet, so the same key exists in several repositories; without thi…
- `repo_path` (string, required)

### `get_poc` (~177 tokens)

Return a finding's PoC so the agent can reproduce the bug while fixing it.

Two sources: the PoC ``scan_repo`` persisted (``source: "database"``), else the
deterministic template for that rule (``source: "deterministic"``,
\``persisted: false`` — run scan_repo to store it). Neither exists →
\``error_code: "NOT_FOUND"``: that rule has no template and no LLM PoC was
produced (no LLM key, or confidence below the PoC threshold). Destructive
templates are never attached by the generator, so never returned here.

The PoC is code generated from untrusted repository content: read it, do not
execute it outside a sandbox.

Input parameters:

- `finding_key` (string, required)
- `project` (string)

### `verify_findings` (~90 tokens)

Verify several findings in one call — same per-key verdicts as verify_finding.

Saves the round-trips, not the work: each key still gets its PoC run. Capped
at ``limit`` keys per call (default 25, each PoC run costs seconds).

Input parameters:

- `keys` (array, required)
- `limit` (integer)
- `repo_path` (string, required)

### `doctor` (~67 tokens)

Self-check: why a tool degraded (sandbox, state volume, roots, cache).

Answers the questions that otherwise surface as silent ``persisted: false`` /
\``unavailable``: is the state volume writable, is a sandbox runtime present,
which roots are allowed, is the scan lock busy.

### `list_detectors` (~64 tokens)

List the GSC detectors available to the scan engine.

Read from the detector registry (no hardcoded catalog): each entry carries
its rule_id and human-readable title, plus registry metadata (echelon,
noise tier) and a derived language when the detector targets one.

Output parameters:

- `result` (array)

### `scan_diff` (~167 tokens)

Scan only files changed relative to a git base ref (PR review).

Finds changed files via ``git diff <base> --name-only`` (plus untracked),
runs a GSC scan, and returns findings filtered to those changed files — so
an agent reviews just what a PR introduced, not the whole repo.

Input parameters:

- `base` (string): git ref to diff against (default "HEAD"; use "origin/main" in CI). Must be a plain ref — anything that looks like an option (``--output=...``, ``-p``) is refused with ``error_code: "REFUSED"``.
- `profile` (string): scan profile (audit, developer-review, ci).
- `repo_path` (string, required): absolute or relative path to the repository.

## Diagnostics

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

## Score history

- 2026-11-05: 41
- 2026-11-04: 40
- 2026-11-03: 40
- 2026-11-02: 39
- 2026-11-01: 39
- 2026-10-31: 38
- 2026-10-30: 38
- 2026-10-29: 37
- 2026-10-28: 37
- 2026-10-27: 37
- 2026-10-26: 36
- 2026-10-25: 37

## Common questions

### What is the GSC Scanner MCP server?

GSC Scanner is an MCP server listed in the public MCP registry as io.github.poliakarmai/gsc-scanner. Local security scanner for AI agents: SAST, SCA, secrets, IaC; verifies exploit and fix. This page covers its container image (ghcr.io/poliakarmai/gsc-scanner).

### Is the GSC Scanner MCP server safe to use?

GSC Scanner scores 41 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 GSC Scanner MCP server expose?

GSC Scanner exposes 10 tools: scan_repo, list_findings, verify_finding, verify_fix, get_finding, and 5 more. Their descriptions and schemas cost roughly 1,205 tokens of context every time the server is loaded.

### Is the GSC Scanner MCP server still maintained?

GSC Scanner 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 did VerifyMCP test on the GSC Scanner MCP server?

VerifyMCP ran 12 checks on GSC Scanner, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about GSC Scanner: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/poliakarmai/gsc-scanner
- Repository: https://github.com/poliakarmai/gsc
- Changelog RSS feed: https://verifymcp.io/servers/poliakarmai-gsc-scanner/ghcr-io-poliakarmai-gsc-scanner.xml
- Changelog JSON feed: https://verifymcp.io/servers/poliakarmai-gsc-scanner/ghcr-io-poliakarmai-gsc-scanner/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/poliakarmai-gsc-scanner/ghcr-io-poliakarmai-gsc-scanner.json
- HTML version of this page: https://verifymcp.io/servers/poliakarmai-gsc-scanner/ghcr-io-poliakarmai-gsc-scanner