cronstable
Related Servers
Alternatives to cronstable
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA read-only server that enables AI agents to triage Kubernetes CronJobs in a single tool call: whether runs happened and stayed on schedule, whether durations are trending slower or overrunning, which jobs have silently stopped succeeding, and why a given run failed, with evidence and stated basis for each verdict. It also lists active runs and recent failures while enforcing namespace allowlists and no write access.844 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only production observability through a small set of tools for health, job status, latest data, approved logs, and deployment metadata, enabling AI planning and review without a production write path.MIT
- AlicenseBqualityCmaintenanceEnables read-only operational audits of schedulers, recurring job health, delivery failures, overdue runs, gateway/MCP health, and lock-file inventory without modifying inspected systems.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect a Crossplane control plane read-only, discovering managed, composite and claim resources, tracing composition trees, and explaining failures with events and reasons. It also surfaces package health, composition definitions and validation, environment and runtime configs, and overall diagnostics across multiple clusters.9Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to OpenClaw and Codex operational data like status, tasks, sessions, logs, and Git changes. Ensures safety via redaction, allowlists, and bounded outputs.MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP service for production troubleshooting that lets you register database, log, code, and message-queue connections in a web console, then have AI clients query them safely by target name. Models never supply hosts, accounts, or passwords themselves, and all operations are restricted to a read-only whitelist with audit logging.3MIT
TDQS
Scored across 19 tools
Nearly every description explicitly names its sibling tools and states when to prefer them (e.g. cron_get_job_resources vs cron_get_node vs cron_query_metrics), which makes the set unusually easy to navigate. The remaining overlap is real but small: cron_validate_schedule and cron_explain_schedule both decode an expression and list upcoming runs, and cron_get_status vs cron_list_jobs differ mainly in emphasis.
All 19 tools share the cron_ prefix and mostly follow a verb_noun shape (cron_get_job, cron_list_runs, cron_validate_schedule, cron_suggest_slot). A few break the pattern with noun or question forms (cron_schedule_pressure, cron_schedule_duplicates, cron_why_no_run), which are readable but less predictable.
19 tools is on the heavy side, but the domain genuinely spans three areas — job/run inspection, schedule authoring helpers, and cluster/host observability — and each tool covers a distinct slice of those. No tool looks like filler, though the observability tail (fleet, node, cluster, metrics, version) is where trimming would be easiest.
The read/diagnostic surface is thorough (status, details, runs, trends, resources, logs, schedule math, cluster view), but the entire mutation lifecycle is absent: no create/update/delete job, no enable/disable, no run-now. cron_list_pools even points at a cron_cancel_queued tool that is not in this set, so agents will hit a dead end when they try to act rather than observe.