Watchdog · light profile

mcp.kituwa.com · Watchdog

What is running, when it last checked in, and what failed. Six checks, computed for this request and cached for at most 60 seconds. No hardcoded green.

State

OKoverall
6/6checks passing
0degraded or unknown
0failing
3schecked at 2026-11-21 22:19:36 UTC

Current state only. No history store on this light profile. Current state is measured; a percentage would be invented.

Schedule

Mode
Request driven, no scheduler
Checks
Checks recompute on request and are cached for at most 60 seconds. The registry is refreshed by the estate orchestrator; this site never writes it.
Previous
computed for this request · 3s ago
Next
next request after the 60 s cache window
Tracking since
2026-11-21
Registry
last written 17m ago by the estate orchestrator (this site never writes it)
Deploy
app/main.py last modified 9m ago; version 1.0.0

Weekly progress

-Sunno runs
-Monno runs
-Tueno runs
-Wedno runs
-Thuno runs
-Frino runs
-Satno runs

Each tile is one local day. Grey means no run was recorded, because this light profile has no scheduler and no history store. Nothing is inferred from a missing row.

Checks

site reachable answered this request · 23 registry entriesregistry loaded in 0.1 ms; in-process probe (no external hop); problems: 0 ok0.1 ms
tls TLSv1.3 · certificate validmcp.kituwa.com:443 verified; notAfter Feb 19 21:01:22 2027 GMT ok83.1 ms
reverse tunnel mcp-kituwa-tunnel.service is activesystemctl is-active mcp-kituwa-tunnel.service -> active; forwards 127.0.0.1:8221 on AWS-001 to 127.0.0.1:8220 here ok
driver link xtest online · disarmed · up 18sGET http://127.0.0.1:8340/healthz -> 200; armed=False ok16.9 ms
registry freshness 23 MCPs · updated 2026-11-21 22:01:49 UTCmcp-registry.json mtime 2026-11-21 22:01:49 UTC (17m ago); 23 entries, 286 tools; problems: 0; undocumented tools: 7 ok
deploy freshness version 1.0.0 · built 9m agonewest of main.py, VERSION at 2026-11-21 22:09:56 UTC ok

Every row shows its own evidence and check time (2026-11-21 22:19:36 UTC). A row is only green when the check actually succeeded; "unknown" is used when a check cannot run in this environment rather than being counted as a pass.

Recent runs

No runs recorded. This site has no scheduler: checks exist only as request-time measurements, so there is no run log to show. The unit that would schedule them lives in deploy/systemd/ and is not installed on the light profile.

Uptime and failures

No history store on this light profile. Current state is measured; a percentage would be invented. Current failures: 0. Degraded or unknown: 0. Machine-readable: /watchdog.json.

What this covers

Covers: the app answering and the registry loading, the TLS certificate of the public origin, the reverse-tunnel systemd unit, the local mouse-driver health endpoint, registry file freshness and entry count, and deploy artifact freshness. Does not cover: a real operator sign-in by a person, the mouse driver's motion correctness, uptime percentages, or any other host.