silentwatch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SILENTWATCH_SYSLOG | No | Path to syslog file for crontab backend (used when backend=crontab) | /var/log/syslog |
| SILENTWATCH_BACKEND | No | Backend type: mock, openclaw-jsonl, crontab, systemd | mock |
| SILENTWATCH_OPENCLAW_LOGS | No | Directory for OpenClaw JSONL logs (used when backend=openclaw-jsonl) | ~/.openclaw/cron-runs/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_jobsA | Enumerate all known cron jobs with last-run summary. Returns id, name, schedule, last run time + status, runs/successes in last 24h, silent-fail count, overdue flag. |
| get_job_statusA | Detailed status for one job: last run, last success, success rates over 24h + 7d, overdue state, silent-fail indicators on the last run. |
| get_job_runsA | Recent run history for a job (newest first) with timing, exit code, status, silent-fail indicators, output snippet. |
| find_overdue_jobsA | Returns jobs whose schedule indicates they should have run but haven't, beyond a grace window. |
| find_silent_failuresC | Jobs that returned exit code 0 but output was flagged by silent-fail rules (empty output, length anomaly, error keywords, duration anomaly). |
| tail_job_logsB | Most recent N log lines for a job (newest last). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| diagnose-overdue | Diagnose why a specific cron job is overdue |
| summarize-cron-health | Daily digest of cron activity, anomalies, and silent failures |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All cron jobs | JSON list of all known jobs with summary state |
| Job: Web Search Refresh | Manifest + run history for web-search-refresh |
| Job: Daily Summary Email | Manifest + run history for daily-summary |
| Job: Audit Snapshot (production) | Manifest + run history for audit-snapshot |
| Job: Skill Registry Integrity Check | Manifest + run history for skill-registry-check |
| Job: Cleanup Logs Older Than 30 Days | Manifest + run history for cleanup-old-logs |
| Job: Per-Agent Cost Report | Manifest + run history for cost-report-generator |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/temurkhan13/silentwatch-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server