Labsco
temurkhan13 logo

silentwatch-mcp

from temurkhan13

MCP server for catching cron silent failures — jobs that exit 0 with empty output, retry storms, action-budget leaks. 6 silent-fail patterns across system cron, systemd timers, OpenClaw cron logs.

🔥🔥🔥🔥✓ VerifiedFreeAdvanced setup
#email#automation#slack#notion#calendar#cloud#devops#git

silentwatch-mcp

MCP server for catching cron silent failures — when scheduled jobs exit 0 with empty output, when retry storms run away, when action budgets leak. Surfaces overdue jobs, length anomalies, and silent-fail patterns to any Claude or MCP-aware agent. Works with system cron, systemd timers, OpenClaw cron logs, and any JSONL run-log out of the box. Keywords: AI agent monitoring, cron health, scheduled-task observability, production AI ops.

What it does

Real silent failures from production AI deployments in the last 30 days:

These all map to one underlying problem: exit-code monitoring lies. The job returned 0; the data is broken anyway. Any team running scheduled jobs has hit at least one of these:

  • Silent failure — the job ran, returned exit code 0, but produced no useful output (a web-search cron returning empty, a backup that wrote a 0-byte file, a digest email that sent with <no rows> in the body). Traditional monitoring sees a green checkmark; the data is broken anyway.
  • Overdue without alert — a job stopped running for 3 days; nobody noticed because nobody was watching
  • Last-success drift — the job runs every hour but only succeeded once in the last 12 attempts; everyone assumes it's healthy because the most recent run was green
  • Audit-trail gap — you need to know when a specific job last completed for a compliance check, and the only "log" is journalctl output that rotated last week

silentwatch-mcp exposes that visibility as MCP tools your AI agent can query directly. No metrics pipeline, no separate dashboard, no SaaS subscription.

> claude: which of my cron jobs have silent failures in the last 24 hours?
[MCP tool: find_silent_failures]
3 jobs flagged:
  • web-search-refresh — ran 12× successfully but output empty in 8 (66% silent fail rate)
  • daily-summary — ran 1× successfully (24× expected); output normal
  • audit-snapshot — last success 5 days ago, all subsequent runs returned exit 0 with empty body

Why silentwatch-mcp

Three things existing tools (Cronitor, Healthchecks.io, Datadog, Prometheus) don't do:

  1. Detect silent failures, not just exit codes. Traditional cron monitoring assumes exit 0 = success. We check the output against configurable rules: empty output, length anomaly vs historical median, error keywords in stdout despite exit 0, duration anomaly. The job that "ran successfully" but returned nothing useful — that's the failure mode that hides for weeks. We catch it.
  2. MCP-native, no integration layer. Claude Desktop, Cline, Continue, OpenClaw agents — any MCP-aware client queries directly. No Grafana plugin, no API wrapper, no JSON to parse manually.
  3. Multi-source out of the box. OpenClaw native JSONL logs, system crontab (/etc/crontab + /etc/cron.d/* + per-user crontab -l), and systemd timers (systemctl list-timers + journalctl) — all four backends ship in v0.3, so you can run silentwatch-mcp against whatever scheduler you have. No vendor lock-in.

Built for the SMB self-hoster running a $40 VPS where Datadog is overkill and a "$0/mo open-source MCP" is the right price point — but the silent-failure detection is just as valuable on enterprise infra.

Tool surface

The server registers these MCP tools (full spec in SPEC.md):

ToolWhat it does
list_jobsEnumerate all known cron jobs with last-run summary
get_job_status(job_id)Detailed status for one job: last run, last success, success rate over window
get_job_runs(job_id, limit)Recent run history with timing + status + output snippet
find_overdue_jobsJobs whose schedule says they should have run but haven't
find_silent_failures(window_hours)Jobs that ran "successfully" but output looks suspicious
tail_job_logs(job_id, lines)Recent log output for one job

Resources:

  • cron://jobs — list of all jobs (manifest)
  • cron://job/{id} — individual job manifest + recent runs
  • cron://run/{id} — individual run instance with full output

Prompts:

  • diagnose-overdue — diagnostic prompt template for an overdue job
  • summarize-cron-health — daily digest of cron activity + anomalies

Roadmap

VersionScopeStatus
v0.1Protocol wiring, mock backend, all 6 tools registered with stub data, tests pass✅ Complete
v0.2OpenClaw JSONL backend implemented (real cron run parsing, malformed-line handling, silent-fail enrichment)✅ Complete (2026-05-02)
v0.3Crontab + systemd backends; cron-schedule parsing for real overdue detection (croniter); 35 new tests✅ Complete (2026-05-02)
v1.0Polish: PyPI release, GitHub Actions CI, MCP registry submissions (Glama + PulseMCP), refined silent-fail rule configuration⏳ Phase 1 ship target (W3, May 18)
v1.xAdditional backends (Cowork scheduler, Claude Code background tasks, generic JSON config), webhook emitter for alerts⏳ Phase 2+

Need this adapted to your stack?

silentwatch-mcp ships with 4 backends (mock, OpenClaw JSONL, crontab, systemd). If your scheduler is something else — AWS EventBridge, GCP Cloud Scheduler, Hangfire, Sidekiq, Temporal, Apache Airflow, Prefect, Dagster, or a custom job runner — and you want the same silent-failure-detection MCP visibility surface for it, that's a Custom MCP Build engagement.

TierScopeInvestmentTimeline
SimpleSingle backend adapter for an existing scheduler with documented API (e.g., GCP Cloud Scheduler)$8,000–$10,0001–2 weeks
StandardCustom backend + custom silent-fail rules + integration with your existing alerting (PagerDuty, Slack, etc.)$15,000–$20,0002–4 weeks
ComplexMulti-backend (federated cron across regions / clusters / tenants) + RBAC + audit-log integration + on-call workflow$25,000–$35,0004–8 weeks

To engage:

  1. Email hello@temhan.dev with subject Custom MCP Build inquiry
  2. Include: a 1-paragraph description of your scheduler stack + which tier you're considering
  3. Reply within 2 business days with a 30-min discovery call slot

This server is also part of the AI Production Discipline Framework — the methodology underlying production AI audits I run.

Production AI audits

If you're running production AI and want an outside practitioner to score readiness, find the failure patterns that are already present, and write the corrective-action plan — that's what this MCP is built into supporting. The standalone audit service:

TierScopeInvestmentTimeline
Audit LiteOne system, top-5 findings, written report$1,5001 week
Audit StandardFull audit, all 14 patterns, 5 Cs findings, 90-day follow-up$3,0002–3 weeks
Audit + WorkshopStandard audit + 2-day team workshop + first monthly audit included$7,5003–4 weeks

Same email channel: hello@temhan.dev with subject AI audit inquiry.

Built by Temur Khan — production AI engineer. Contact: hello@temhan.dev