Clearon Ops Audit MCP

Read-only MCP server for deterministic scheduler, runtime, and lock-state audits.

It summarizes recurring-job health, delivery failures, degraded-success patterns, overdue runs, gateway/MCP health, and lock-file inventory without modifying the system it inspects.

What it does

• Lists recurring jobs and summarizes current job health

• Separates execution failures from delivery failures

• Flags repeated degraded-success summaries

• Reports overdue recurring jobs

• Probes gateway, MCP, and approved lock roots in read-only mode

• Generates a combined operational report

What it does not do

• It does not edit cron jobs or configuration

• It does not restart services

• It does not delete lock files

• It does not infer that a lock file is stale just because it exists

Requirements

• Node.js 20 or newer

• The openclaw CLI available on PATH, or OPENCLAW_BIN set explicitly

• A local MCP client that can launch a stdio server

Installation

cd tools/clearon-ops-audit-mcp
npm install
npm test
npm run smoke

MCP client setup

Example stdio configuration:

{
  "mcpServers": {
    "clearon-ops-audit": {
      "command": "node",
      "args": ["/absolute/path/to/clearon-ops-audit-mcp/server.mjs"],
      "env": {
        "CLEARON_OPS_AUDIT_WORKSPACE": "/absolute/path/to/workspace"
      }
    }
  }
}

The workspace defaults to the client process working directory. Override it with CLEARON_OPS_AUDIT_WORKSPACE when lock scanning should target a specific tree.

Commands

npm test
npm run smoke
npm run syntax
npm run report

Tools

• get_server_health

• list_recurring_jobs

• get_job_health

• get_recent_failures

• find_missed_or_overdue_runs

• summarize_degraded_successes

• check_delivery_failures

• probe_registered_mcps

• check_gateway_health

• audit_locks

• generate_ops_report