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

Data observability: alerts, freshness checks and schema drift for your data assets.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/datawatch`
- Version: `0.1.0`
- 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 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1066 tokens (~44/item across 24 items; 24 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 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/datawatch MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

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

## 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 40, +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-11-02 (score 39)

First indexed and scored.

## MCP tools (24)

### `health_summary` (~19 tokens)

Get an overall health summary of the monitored data platform.

### `get_todays_briefing` (~24 tokens)

Get today's briefing of notable data-observability events.

### `get_alerts_summary` (~17 tokens)

Get a summary of current alerts.

### `list_alerts` (~90 tokens)

List alerts, optionally filtered by status, severity, asset, and date range.

Input parameters:

- `asset_id` (string): Asset id filter.
- `from_date` (string): Earliest alert date to include, YYYY-MM-DD.
- `severity` (string): Severity filter.
- `status` (string): Alert status filter.
- `to_date` (string): Latest alert date to include, YYYY-MM-DD.

### `list_inbox_alerts` (~49 tokens)

List alerts in the inbox, optionally filtered by status and capped by limit.

Input parameters:

- `limit` (integer): Maximum number of alerts to return.
- `status` (string): Alert status filter.

### `update_alert` (~58 tokens)

Apply an action to an alert, with an optional comment.

Input parameters:

- `action` (string, required): Action to apply to the alert.
- `alert_id` (string, required): Alert id to update.
- `comment` (string): Optional comment recorded with the action.

### `get_alert_trends` (~33 tokens)

Get alert trends, optionally for a given period.

Input parameters:

- `period` (string): Period to compute alert trends over.

### `get_alert_history` (~32 tokens)

Get the history of an alert by id.

Input parameters:

- `alert_id` (string, required): Alert id whose history to fetch.

### `list_alert_rules` (~50 tokens)

List alert rules, optionally filtered by asset and active flag.

Input parameters:

- `asset_id` (string): Asset id filter.
- `is_active` (boolean): When given, only return rules with this active flag.

### `create_alert_rule` (~59 tokens)

Create an alert rule for an asset with a rule type and optional config.

Input parameters:

- `asset_id` (string, required): Asset id the rule watches.
- `config` (object): Optional rule configuration object.
- `rule_type` (string, required): Alert rule type.

### `manage_alert_rule` (~45 tokens)

Apply a management action to an alert rule by id.

Input parameters:

- `action` (string, required): Management action to apply to the rule.
- `rule_id` (string, required): Alert rule id.

### `list_assets` (~56 tokens)

List data assets, optionally filtered by source, asset type, and search text.

Input parameters:

- `asset_type` (string): Asset type filter.
- `search` (string): Free-text search over assets.
- `source` (string): Source filter.

### `create_asset` (~56 tokens)

Create a data asset with a name and source type, plus optional connection config.

Input parameters:

- `connection_config` (object): Optional connection configuration object.
- `name` (string, required): Asset name.
- `source_type` (string, required): Asset source type.

### `manage_asset` (~43 tokens)

Apply a management action to a data asset by id.

Input parameters:

- `action` (string, required): Management action to apply to the asset.
- `asset_id` (string, required): Asset id.

### `trigger_asset_discovery` (~33 tokens)

Trigger discovery for a data asset by id.

Input parameters:

- `asset_id` (string, required): Asset id to run discovery for.

### `get_freshness_summary` (~21 tokens)

Get a summary of data freshness across monitored assets.

### `check_freshness` (~53 tokens)

Check freshness for an asset, optionally for a specific table path.

Input parameters:

- `asset_id` (string, required): Asset id to check freshness for.
- `table_path` (string): Optional table path to check within the asset.

### `setup_freshness` (~69 tokens)

Set up freshness monitoring for an asset's table, with an optional check interval.

Input parameters:

- `asset_id` (string, required): Asset id to set up freshness monitoring for.
- `check_interval` (string): Optional check interval for the freshness checks.
- `table_path` (string, required): Table path to monitor.

### `list_freshness_schedules` (~32 tokens)

List freshness schedules, optionally filtered by asset.

Input parameters:

- `asset_id` (string): Asset id filter.

### `manage_freshness_schedule` (~48 tokens)

Apply a management action to a freshness schedule by id.

Input parameters:

- `action` (string, required): Management action to apply to the schedule.
- `schedule_id` (string, required): Freshness schedule id.

### `get_schema_summary` (~19 tokens)

Get a summary of schema monitoring and recent drift.

### `list_schema_changes` (~79 tokens)

List schema changes, optionally filtered by asset, severity, and date range.

Input parameters:

- `asset_id` (string): Asset id filter.
- `from_date` (string): Earliest change date to include, YYYY-MM-DD.
- `severity` (string): Severity filter.
- `to_date` (string): Latest change date to include, YYYY-MM-DD.

### `create_schema_baseline` (~45 tokens)

Create a schema baseline for an asset, with an optional description.

Input parameters:

- `asset_id` (string, required): Asset id to baseline.
- `description` (string): Optional baseline description.

### `get_schema_monitoring` (~36 tokens)

Get schema monitoring status for an asset by id.

Input parameters:

- `asset_id` (string, required): Asset id to get schema monitoring status for.

## Diagnostics

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

## Score history

- 2026-11-05: 40
- 2026-11-04: 40
- 2026-11-03: 39
- 2026-11-02: 39

## Common questions

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

io.github.CloudCorpRecords/datawatch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/datawatch. Data observability: alerts, freshness checks and schema drift for your data assets. This page covers its container image (ghcr.io/cloudcorprecords/datawatch).

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

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

io.github.CloudCorpRecords/datawatch exposes 24 tools: health_summary, get_todays_briefing, get_alerts_summary, list_alerts, list_inbox_alerts, and 19 more. Their descriptions and schemas cost roughly 1,066 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/datawatch 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/datawatch MCP server under?

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