io.github.CloudCorpRecords/tracewatch

tracewatch

Is the io.github.CloudCorpRecords/tracewatch MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-26.

Observability, tracking, and root-cause for Security Wave scans and findings.

alive probed 2026-11-14 · unchanged since 2026-10-26

7tools

1.8ktokens in Claude

0.9 %of Claude's 200k window

0.7×the median server

384 msto initialize

10 msto list tools

Run it: npx -y @reneturcios/tracewatch@0.2.2 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: tracewatch 0.2.2
Capabilities: tools
Instructions: none
Of a 1M window: 0.2 % of a 1M context window
Count: 1.8k tokens in Claude, exact, measured 2026-10-25. With the Claude Code prefix mcp__…__ on each tool name: 1.9k. The o200k_base estimate is 1.1k. Counted again when the tool definitions change. Method.
Repository: https://github.com/CloudCorpRecords/tracewatch
Registry: active, updated 2026-10-26 · 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.70×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
ingest_scan	347	204	19 %
finding_provenance	317	186	17 %
explain_finding	295	173	16 %
list_findings	286	168	15 %
diff_scans	274	161	15 %

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

Servers that mention observability or findings.

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.