io.github.CloudCorpRecords/datawatch

datawatch

Is the io.github.CloudCorpRecords/datawatch MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-03.

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

alive probed 2026-11-14 · unchanged since 2026-11-03

24tools

2.9ktokens in Claude Opus 5.5

1.5 %of Claude's 200k window

1.2×the median server

249 msto initialize

5 msto list tools

Run it: npx -y @reneturcios/datawatch@0.1.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: datawatch 0.1.0
Capabilities: tools
Instructions: none
Of a 1M window: 0.3 % of a 1M context window
Count: 2.9k tokens in Claude Opus 5.5, exact, measured 2026-11-03. With the Claude Code prefix mcp__…__ on each tool name: 3.1k. The o200k_base estimate is 1.5k. Counted again when the tool definitions change. Method.
Repository: https://github.com/CloudCorpRecords/datawatch
Registry: active, updated 2026-11-02 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.91×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
list_alerts	220	115	8 %
list_schema_changes	193	101	7 %
setup_freshness	185	97	6 %
create_alert_rule	166	87	6 %
update_alert	162	85	6 %

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention observability or freshness.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.