Datawatch

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

Datawatch's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Datawatch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

datawatch

datawatch talks to a data-observability platform's API: platform health and a daily briefing, alerts (summaries, inbox, trends, history and rules), the data assets under observation and their discovery, freshness summaries, checks and schedules, and schema summaries, change lists, baselines and monitoring. One binary serves a command-line interface and a stdio MCP server.

An API key is required. Set ARMOR_API_KEY before use; when it is missing or blank, every tool fails with an error naming the variable before any request is made. The API base URL can be overridden with DATAWATCH_API_URL; when it is not set, calls go to https://api.anomalyarmor.ai (a labelled reconstruction).

Scope note: the platform's documentation enumerates 52 tool names (its own heading says 29 and its version line says 52; the enumerated sections list 52). datawatch implements a labelled core subset of 24 of them — alerts, assets, freshness and schema drift — and omits the metrics, validity, referential, destination, coverage, recommendation, Q&A, intelligence, lineage, job, tag and API-key tools.

Install

bash
npx @reneturcios/datawatch get_alerts_summary

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/datawatch

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

The subcommands mirror the MCP tool names:

bash
export ARMOR_API_KEY=...
datawatch health_summarydatawatch get_todays_briefingdatawatch list_alerts --status open --severity highdatawatch list_inbox_alerts --limit 20datawatch update_alert --alert-id al1 --action acknowledge --comment "looking into it"datawatch get_alert_trends --period 7ddatawatch list_alert_rules --asset-id a1 --is-active truedatawatch create_alert_rule --asset-id a1 --rule-type freshness --config '{"threshold_hours":24}'datawatch list_assets --source snowflake --search ordersdatawatch create_asset --name warehouse --source-type snowflakedatawatch trigger_asset_discovery --asset-id a1datawatch check_freshness --asset-id a1 --table-path db.schema.ordersdatawatch setup_freshness --asset-id a1 --table-path db.schema.orders --check-interval 1hdatawatch list_schema_changes --severity breakingdatawatch create_schema_baseline --asset-id a1 --description initialdatawatch get_schema_monitoring --asset-id a1
datawatch --version

Results print the upstream JSON payload. Exit codes: 0 on success, 1 when a call fails (including a missing key or an upstream API error), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/datawatch mcp

MCP client configuration:

json
{  "mcpServers": {    "datawatch": {      "command": "npx",      "args": ["-y", "@reneturcios/datawatch", "mcp"],      "env": { "ARMOR_API_KEY": "..." }    }  }}

Tools

ToolInputWhat it does
health_summary(none)Overall platform health summary.
get_todays_briefing(none)Today's observability briefing.
get_alerts_summary(none)Summary of current alerts.
list_alertsstatus, severity, asset_id, from_date, to_dateList alerts with optional filters.
list_inbox_alertsstatus, limit (integer)List inbox alerts.
update_alertalert_id, action (both required), commentApply an action to an alert.
get_alert_trendsperiodAlert trends for a period.
get_alert_historyalert_id (required)History of one alert.
list_alert_rulesasset_id, is_active (boolean)List alert rules.
create_alert_ruleasset_id, rule_type (both required), config (object)Create an alert rule.
manage_alert_rulerule_id, action (both required)Manage an alert rule.
list_assetssource, asset_type, searchList data assets.
create_assetname, source_type (both required), connection_config (object)Create a data asset.
manage_assetasset_id, action (both required)Manage a data asset.
trigger_asset_discoveryasset_id (required)Trigger asset discovery.
get_freshness_summary(none)Freshness summary across assets.
check_freshnessasset_id (required), table_pathCheck one asset's freshness.
setup_freshnessasset_id, table_path (both required), check_intervalSet up freshness monitoring.
list_freshness_schedulesasset_idList freshness schedules.
manage_freshness_scheduleschedule_id, action (both required)Manage a freshness schedule.
get_schema_summary(none)Schema monitoring summary.
list_schema_changesasset_id, severity, from_date, to_dateList schema changes.
create_schema_baselineasset_id (required), descriptionCreate a schema baseline.
get_schema_monitoringasset_id (required)Schema monitoring for one asset.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit 7a75183

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts