← Back to Skills Marketplace
reikys

Mcp Health Monitor

by reikys · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
111
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install mcp-health-monitor
Description
Auto-monitor MCP servers and AI services with health checks, auto-restart on failure, and Telegram alerts
Usage Guidance
This skill appears to do what it says: local health checks, optional Telegram alerts, and macOS launchctl restarts. Before installing: (1) open and review scripts/healthcheck.sh and the SERVICES array and adjust patterns so pgrep -f won't accidentally match unrelated processes; (2) if you use a .env file, ensure it contains only VAR=VALUE lines and is owned and writable only by your user (sourcing the file executes shell code); (3) test the script manually before enabling a scheduled LaunchAgent/cron job; (4) verify the Telegram bot token and chat ID are correct and that alerts go only to your intended chat; (5) on Linux, adapt the restart commands to systemctl instead of launchctl. If you are comfortable with these checks, the skill is coherent with its stated purpose.
Capability Analysis
Type: OpenClaw Skill Name: mcp-health-monitor Version: 1.0.0 The skill is a legitimate monitoring utility designed to check the health of MCP servers and AI services. The core logic in `scripts/healthcheck.sh` uses standard tools like `curl` and `pgrep` to verify service status and employs `launchctl` for service restarts as advertised. The Telegram alert functionality and environment variable handling are transparently implemented and align with the documentation in `SKILL.md` and `README.md`.
Capability Assessment
Purpose & Capability
Name/description, README, SKILL.md, and the included script all describe the same behavior: HTTP and process checks, optional Telegram alerts, and macOS launchctl restarts. There are no unexplained environment variables, external services, or binaries requested beyond those needed (curl/pgrep/launchctl which are expected for this task).
Instruction Scope
Runtime instructions and the script stay within monitoring/restart/alert scope. Notable points: the script sources an ENV_FILE (default $HOME/.env) which will execute any shell constructs present there (the script uses `source`), so the file must be restricted to simple VAR=VALUE entries and owned by the user. Process checks use `pgrep -f` with user-supplied patterns — overly-broad patterns can match unintended processes (false positives/negatives). Alerts are sent only to Telegram's API (https://api.telegram.org) as expected; no other external endpoints are contacted.
Install Mechanism
No install spec — instruction-only with an included shell script. This is low-risk from an installation perspective: nothing is downloaded from remote URLs and nothing is automatically written to system locations by an installer. The user is instructed to copy the script and create a LaunchAgent or cron entry manually.
Credentials
No required secrets are declared in registry metadata; the script optionally uses TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID for alerts, which is proportionate. Caveat: the script sources the ENV_FILE which could execute commands if the file contains shell statements rather than simple assignments; treat the .env file as executable content and protect it accordingly.
Persistence & Privilege
The skill does not request 'always: true' or other elevated platform privileges. The installation instructions recommend creating a user LaunchAgent or cron entry to run periodically — this gives persistent scheduling (intended for monitoring) but is a normal and expected level of persistence for a health-check tool.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install mcp-health-monitor
  3. After installation, invoke the skill by name or use /mcp-health-monitor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of mcp-health-monitor: - Automates health checks for MCP servers and AI services (HTTP and process checks). - Auto-restarts failed services via launchctl; supports optional Telegram alerts for failures. - Simple setup with environment variables and an editable services list in the script. - macOS LaunchAgent and Linux (cron/systemd) scheduling supported. - Detailed, structured logs and failure notifications only when issues are detected.
Metadata
Slug mcp-health-monitor
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Mcp Health Monitor?

Auto-monitor MCP servers and AI services with health checks, auto-restart on failure, and Telegram alerts. It is an AI Agent Skill for Claude Code / OpenClaw, with 111 downloads so far.

How do I install Mcp Health Monitor?

Run "/install mcp-health-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Mcp Health Monitor free?

Yes, Mcp Health Monitor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Mcp Health Monitor support?

Mcp Health Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Mcp Health Monitor?

It is built and maintained by reikys (@reikys); the current version is v1.0.0.

💬 Comments