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

Observability, tracking, and root-cause for Security Wave scans and findings.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/tracewatch`
- Version: `0.2.1`
- 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-10-23.

- **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 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 728 tokens (~104/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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/tracewatch MCP server?

io.github.CloudCorpRecords/tracewatch runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/tracewatch:0.2.1. 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-tracewatch -- docker run --rm -i ghcr.io/cloudcorprecords/tracewatch:0.2.1
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

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

## 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-10-23 (score 40, 0)

- [functional] Package version: 0.1.0 → 0.2.1
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-10-22 (score 40)

First indexed and scored.

## MCP tools (7)

### `ingest_scan` (~131 tokens)

Run hookcheck, actionpin, injectcheck, mcpvet, depguard, and flowcheck against a local repo path and store the results as a timestamped scan record with stable finding IDs. Returns the scan record and every finding observation. Use this to start or refresh tracking for a repo.

Input parameters:

- `name` (string): Repo key to file the scan under (default: GitHub slug from the git remote, else the directory name)
- `path` (string, required): Local path of the repo or directory to scan
- `tools` (array): Subset of tools to run (default: all six)

### `diff_scans` (~116 tokens)

Diff two scans of a repo (default: the last two). Reports NEW, RESOLVED, and CHANGED findings, verdict moves, and action ref events with both refs spelled out, including pin regressions (PINNED to MUTABLE or BRANCH) and bare ref moves on pinned actions.

Input parameters:

- `from` (string): Earlier scanId (default: the scan before `to`)
- `repo` (string, required): Repo key used at ingest
- `to` (string): Later scanId (default: the latest scan)

### `finding_provenance` (~139 tokens)

Root-cause provenance for one finding: the introducing commit from git pickaxe on the finding's content, the current-line commit from git blame, the associated GitHub PR when the API answers, and the finding's ref history from the scan store. Confirmed evidence, inferences, and unestablished items are reported separately; nothing is guessed.

Input parameters:

- `findingId` (string, required): Full findingId (tw_...) or a prefix of at least 8 characters
- `path` (string): Local clone path to run git evidence against (default: the path recorded at ingest)
- `repo` (string, required): Repo key used at ingest

### `repo_health` (~71 tokens)

Health report for a repo across all its scans: verdict trend, open findings by tool and severity, resolved count, mean time open for resolved findings, all action ref events, and watch detection latency stats (count, median, max time-to-detect).

Input parameters:

- `repo` (string, required): Repo key used at ingest

### `watch_status` (~58 tokens)

Summarize the tracewatch store: every tracked repo with its scan count, last scan time, open finding count, detection count, and median time-to-detect. Use this to see what is being watched and tracked before drilling into one repo.

### `list_findings` (~89 tokens)

List tracked findings for a repo with derived status. Filter by tool, severity, and status (open, resolved, or all; default open). Each entry carries the stable findingId usable with finding_provenance and explain_finding.

Input parameters:

- `repo` (string, required): Repo key used at ingest
- `severity` (string)
- `status` (string)
- `tool` (string)

### `explain_finding` (~124 tokens)

The full evidence bundle for one finding, written to act on: the tracked finding (status, first and last seen, content versions), its scan history is summarized in the provenance record, and the provenance itself (introducing commit, PR, ref history, confirmed versus inferred versus not established).

Input parameters:

- `findingId` (string, required): Full findingId (tw_...) or a prefix of at least 8 characters
- `path` (string): Local clone path for git evidence (default: the path recorded at ingest)
- `repo` (string, required): Repo key used at ingest

## Diagnostics

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

## Score history

- 2026-10-23: 40
- 2026-10-22: 40

## Common questions

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

io.github.CloudCorpRecords/tracewatch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/tracewatch. Observability, tracking, and root-cause for Security Wave scans and findings. This page covers its container image (ghcr.io/cloudcorprecords/tracewatch).

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

io.github.CloudCorpRecords/tracewatch scores 40 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/tracewatch MCP server expose?

io.github.CloudCorpRecords/tracewatch exposes 7 tools: ingest_scan, diff_scans, finding_provenance, repo_health, watch_status, and 2 more. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.

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

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

io.github.CloudCorpRecords/tracewatch 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/tracewatch
- Repository: https://github.com/CloudCorpRecords/tracewatch
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-tracewatch/ghcr-io-cloudcorprecords-tracewatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-tracewatch/ghcr-io-cloudcorprecords-tracewatch.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-tracewatch/ghcr-io-cloudcorprecords-tracewatch