io.github.CloudCorpRecords/datawatch
OCI · GHCR.IO/CLOUDCORPRECORDS/DATAWATCH · 2 COMPONENTS
Data observability: alerts, freshness checks and schema drift for your data assets.
Available components
Last scanned (5 hours ago)
Scores higher than 42% 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1066 tokens (~44/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 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.
- 4 Nov 26 +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.
- 2 Nov 26 39
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 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/datawatch@0.1.0
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 →
check_freshness ~53
Check freshness for an asset, optionally for a specific table path.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset id to check freshness for. |
| table_path | string | – | Optional table path to check within the asset. |
No output schema declared.
No examples provided.
create_alert_rule ~59
Create an alert rule for an asset with a rule type and optional config.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset id the rule watches. |
| config | object | – | Optional rule configuration object. |
| rule_type | string | yes | Alert rule type. |
No output schema declared.
No examples provided.
create_asset ~56
Create a data asset with a name and source type, plus optional connection config.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_config | object | – | Optional connection configuration object. |
| name | string | yes | Asset name. |
| source_type | string | yes | Asset source type. |
No output schema declared.
No examples provided.
create_schema_baseline ~45
Create a schema baseline for an asset, with an optional description.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset id to baseline. |
| description | string | – | Optional baseline description. |
No output schema declared.
No examples provided.
get_alert_history ~32
Get the history of an alert by id.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | Alert id whose history to fetch. |
No output schema declared.
No examples provided.
get_alert_trends ~33
Get alert trends, optionally for a given period.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Period to compute alert trends over. |
No output schema declared.
No examples provided.
get_alerts_summary ~17
Get a summary of current alerts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_freshness_summary ~21
Get a summary of data freshness across monitored assets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_schema_monitoring ~36
Get schema monitoring status for an asset by id.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset id to get schema monitoring status for. |
No output schema declared.
No examples provided.
get_schema_summary ~19
Get a summary of schema monitoring and recent drift.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_todays_briefing ~24
Get today's briefing of notable data-observability events.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
health_summary ~19
Get an overall health summary of the monitored data platform.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_alert_rules ~50
List alert rules, optionally filtered by asset and active flag.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | – | Asset id filter. |
| is_active | boolean | – | When given, only return rules with this active flag. |
No output schema declared.
No examples provided.
list_alerts ~90
List alerts, optionally filtered by status, severity, asset, and date range.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_assets ~56
List data assets, optionally filtered by source, asset type, and search text.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Asset type filter. |
| search | string | – | Free-text search over assets. |
| source | string | – | Source filter. |
No output schema declared.
No examples provided.
list_freshness_schedules ~32
List freshness schedules, optionally filtered by asset.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | – | Asset id filter. |
No output schema declared.
No examples provided.
list_inbox_alerts ~49
List alerts in the inbox, optionally filtered by status and capped by limit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of alerts to return. |
| status | string | – | Alert status filter. |
No output schema declared.
No examples provided.
list_schema_changes ~79
List schema changes, optionally filtered by asset, severity, and date range.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
manage_alert_rule ~45
Apply a management action to an alert rule by id.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Management action to apply to the rule. |
| rule_id | string | yes | Alert rule id. |
No output schema declared.
No examples provided.
manage_asset ~43
Apply a management action to a data asset by id.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Management action to apply to the asset. |
| asset_id | string | yes | Asset id. |
No output schema declared.
No examples provided.
manage_freshness_schedule ~48
Apply a management action to a freshness schedule by id.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Management action to apply to the schedule. |
| schedule_id | string | yes | Freshness schedule id. |
No output schema declared.
No examples provided.
setup_freshness ~69
Set up freshness monitoring for an asset's table, with an optional check interval.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset id to set up freshness monitoring for. |
| check_interval | string | – | Optional check interval for the freshness checks. |
| table_path | string | yes | Table path to monitor. |
No output schema declared.
No examples provided.
trigger_asset_discovery ~33
Trigger discovery for a data asset by id.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset id to run discovery for. |
No output schema declared.
No examples provided.
update_alert ~58
Apply an action to an alert, with an optional comment.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to apply to the alert. |
| alert_id | string | yes | Alert id to update. |
| comment | string | – | Optional comment recorded with the action. |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/cloudcorprecords/datawatch
claude mcp add cloudcorprecords-datawatch -- docker run --rm -i ghcr.io/cloudcorprecords/datawatch:0.1.0
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.