openclaw-health-mcp
Related Servers
Alternatives to openclaw-health-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMulti-machine system monitor with a built-in MCP server that enables AI agents to query health metrics, manage processes, schedule cron jobs, and run diagnostics across local and remote machines.133 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceA real-time system diagnostics MCP server that gives AI agents live access to CPU, RAM, disk, network, processes, and hardware health metrics, with zero cloud dependency.7-
- FlicenseNot gradedqualityDmaintenanceIntegrity monitor for MCP server ecosystems, providing real-time health checks, drift detection, and cascade impact analysis for any AI agent.-
- AlicenseAqualityAmaintenanceAn MCP server that surfaces scheduled-job state and detects silent failures (exit 0 but no useful output) for cron, systemd timers, and OpenClaw schedulers, enabling AI agents to query job health and overdue status directly.627 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for agent network monitoring. Aggregates real-time population counts, transaction volume, and health metrics across multi-service agent infrastructure.MIT
- AlicenseAqualityDmaintenanceLinux system administration via AI agents — MCP server for managing services, processes, disk, network and logs on Linux systems.15MIT
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of system health: CPU/memory, cron, disk, gateway, overall snapshot, upgrades, errors, and skill registry. There is no overlap in purpose, and even the overview tool aggregates rather than duplicates.
All tools use a consistent snake_case naming pattern with a descriptive noun_health or noun_status or noun_check suffix. The names clearly indicate the resource and action, e.g., cpu_memory_health, health_overview, recent_errors.
With 8 tools, the server covers essential health monitoring dimensions for an OpenClaw deployment without being overwhelming. Each tool serves a clear purpose, and the count is typical for a focused MCP server.
The tool set covers CPU, memory, disk, cron, gateway, upgrade status, errors, and skill registry—comprehensive for common health checks. Minor gaps like network connectivity may exist, but references to companion MCPs (silentwatch-mcp, openclaw-skill-vetter-mcp) indicate thoughtful scoping.