Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计通过

mcp-health-monitorMCP health monitor 搜索

Agent Skill

mcp-health-monitor 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,120

周安装

134

GitHub Stars

公开资料未说明

下载量

1,093
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:mcp-health-monitor(MCP health monitor 搜索)
来源仓库:https://github.com/reikys/mcp-health-monitor
安装命令:
openclaw skills install mcp-health-monitor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install mcp-health-monitor

简介

自动监控MCP服务器与AI服务健康状态,支持故障重启与Telegram告警。

  • 适合部署在OpenClaw中保障关键AI服务的高可用运行。
  • 提供心跳检测、异常恢复与通知推送三位一体运维能力。
  • 安装命令:openclaw skills install mcp-health-monitor
  • 配置时需注意Telegram Bot Token等敏感信息的保密处理

SKILL.md

name
mcp-health-monitor
version
1.0.0
description
Auto-monitor MCP servers and AI services with health checks, auto-restart on failure, and Telegram alerts
author
reikys
license
MIT
tags
[mcp, monitoring, health-check, automation, devops]
triggers

MCP Health Monitor

Automated health monitoring for MCP servers and AI services. Detects failures, auto-restarts services via launchctl, and sends Telegram alerts on incidents. Silent when everything is healthy.

Supported Check Types

TypeMethodAuto-Restart
HTTP Healthcurl endpoint checkYes (via launchctl)
Processpgrep process detectionYes (via launchctl)
Process-onlypgrep detectionNo (expects external spawn)

Quick Start

1. Install the healthcheck script

# Copy the script to your preferred location
cp scripts/healthcheck.sh ~/.local/bin/mcp-healthcheck.sh
chmod +x ~/.local/bin/mcp-healthcheck.sh

2. Configure environment variables

Create or update your .env file (path configurable via ENV_FILE):

# Required for Telegram alerts (optional — script works without them)
TELEGRAM_BOT_TOKEN=your-bot-token-here
TELEGRAM_CHAT_ID=your-chat-id-here

3. Configure services to monitor

Edit the SERVICES array in healthcheck.sh. Each entry follows this format:

name|check_type|target|launchctl_label

Fields:

  • name — Display name for logs and alerts
  • check_typehttp (HTTP endpoint) or process (pgrep pattern)
  • target — URL for http checks, or process grep pattern for process checks
  • launchctl_label — macOS launchctl service label for auto-restart (use none to skip restart)

Default configuration:

SERVICES=(
  "Claw-Empire|http|http://127.0.0.1:8790/api/health|com.claw-empire.server"
  "Hermes-Gateway|process|hermes_cli.main gateway|ai.hermes.gateway"
  "mem0-MCP|process|mem0_mcp/server.py|none"
  "Brave-Search-MCP|process|brave-search-mcp-server|none"
  "Context7-MCP|process|context7-mcp|none"
)

4. Set up automated scheduling (macOS LaunchAgent)

Create ~/Library/LaunchAgents/com.mcp-health-monitor.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
  "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>com.mcp-health-monitor</string>
  <key>ProgramArguments</key>
  <array>
    <string>/bin/bash</string>
    <string>~/.local/bin/mcp-healthcheck.sh</string>
  </array>
  <key>StartInterval</key>
  <integer>300</integer>
  <key>StandardOutPath</key>
  <string>~/.local/logs/mcp-healthcheck-stdout.log</string>
  <key>StandardErrorPath</key>
  <string>~/.local/logs/mcp-healthcheck-stderr.log</string>
  <key>RunAtLoad</key>
  <true/>
</dict>
</plist>

Load the agent:

launchctl load ~/Library/LaunchAgents/com.mcp-health-monitor.plist

5. Linux alternative (systemd timer or cron)

# crontab -e
*/5 * * * * /path/to/mcp-healthcheck.sh

For systemd, replace launchctl stop/start calls in the script with systemctl restart.

Environment Variables

VariableRequiredDescription
ENV_FILENoPath to .env file (default: $HOME/.env)
LOG_FILENoPath to log file (default: $HOME/.local/logs/mcp-healthcheck.log)
TELEGRAM_BOT_TOKENNoTelegram Bot API token for alerts
TELEGRAM_CHAT_IDNoTelegram chat/group ID for alerts
HTTP_TIMEOUTNoHTTP check timeout in seconds (default: 5)
RESTART_DELAYNoSeconds to wait between stop and start (default: 3)

Log Format

Structured log entries:

[2026-03-30 14:00:00] [Claw-Empire] [OK] healthy (HTTP 200)
[2026-03-30 14:00:00] [mem0-MCP] [FAIL] not running (process not found)
[2026-03-30 14:00:00] [SYSTEM] [ALERT] 1 failures detected — sending notification

Telegram Alert Format

Alerts are only sent when failures are detected. No notification on all-healthy runs.

🚨 *MCP Health Check Alert*
2026-03-30 14:00:00

Failures detected (1):
* mem0-MCP (process not found)

Services with launchctl labels were auto-restarted.
Process-only services await external respawn.

Customization

Adding a new service

Append to the SERVICES array:

SERVICES+=(
  "My-Custom-MCP|process|my-custom-mcp-server|com.my-custom.mcp"
)

HTTP check with custom port

SERVICES+=(
  "My-API|http|http://127.0.0.1:3000/health|com.my-api.server"
)

Disable auto-restart for a service

Set the launchctl label to none:

"My-Service|process|my-service-pattern|none"

Troubleshooting

IssueSolution
Telegram alerts not sendingVerify TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in your .env
launchctl restart failsCheck the service label matches your .plist file name
False positives on process checksAdjust the pgrep pattern to be more specific
Log file growing too largeSet up logrotate or periodic cleanup via cron

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

95.96%
按下载量换算1,049

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills