io.github.CloudCorpRecords/tracewatch
OCI · GHCR.IO/CLOUDCORPRECORDS/TRACEWATCH · 2 COMPONENTS
Observability, tracking, and root-cause for Security Wave scans and findings.
Available components
Last scanned (8 hours ago)
Scores higher than 51% of OCI servers
Category Monitoring and Observability
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 Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 728 tokens (~104/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
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.
- 23 Oct 26 0
- Package version: 0.1.0 → 0.2.1 functional
- Package version: 0.1.0 → 0.1.1 functional
- 22 Oct 26 40
First indexed and scored.
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 23 Oct 2026 · Analysed oci/ghcr.io/cloudcorprecords/tracewatch@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
diff_scans ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Earlier scanId (default: the scan before `to`) |
| repo | string | yes | Repo key used at ingest |
| to | string | – | Later scanId (default: the latest scan) |
No output schema declared.
No examples provided.
explain_finding ~124
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).
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | 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 | yes | Repo key used at ingest |
No output schema declared.
No examples provided.
finding_provenance ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | 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 | yes | Repo key used at ingest |
No output schema declared.
No examples provided.
ingest_scan ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Repo key to file the scan under (default: GitHub slug from the git remote, else the directory name) |
| path | string | yes | Local path of the repo or directory to scan |
| tools | array | – | Subset of tools to run (default: all six) |
No output schema declared.
No examples provided.
list_findings ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Repo key used at ingest |
| severity | string | – | – |
| status | string | – | – |
| tool | string | – | – |
No output schema declared.
No examples provided.
repo_health ~71
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).
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Repo key used at ingest |
No output schema declared.
No examples provided.
watch_status ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
oci · ghcr.io/cloudcorprecords/tracewatch
claude mcp add cloudcorprecords-tracewatch -- docker run --rm -i ghcr.io/cloudcorprecords/tracewatch:0.2.1
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.