Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y [email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
HEALTHCHECKS_API_KEY=<secret> HEALTHCHECKS_URL=<value> HEALTHCHECKS_READ_ONLY=<value> HEALTHCHECKS_ALLOW_TOOLS=<value> HEALTHCHECKS_DENY_TOOLS=<value> HEALTHCHECKS_INSECURE_TLS=<value> claude mcp add io.github.ni-c-healthchecks-mcp -- npx -y healthchecks-mcp@0.3.0在終端機中執行。
{ "mcpServers": { "io.github.ni-c-healthchecks-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "HEALTHCHECKS_API_KEY": "<secret>", "HEALTHCHECKS_URL": "<value>", "HEALTHCHECKS_READ_ONLY": "<value>", "HEALTHCHECKS_ALLOW_TOOLS": "<value>", "HEALTHCHECKS_DENY_TOOLS": "<value>", "HEALTHCHECKS_INSECURE_TLS": "<value>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
尚未爬取 README。 開啟儲存庫
Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed
{ "mcpServers": { "io.github.ni-c-healthchecks-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "HEALTHCHECKS_API_KEY": "<secret>", "HEALTHCHECKS_URL": "<value>", "HEALTHCHECKS_READ_ONLY": "<value>", "HEALTHCHECKS_ALLOW_TOOLS": "<value>", "HEALTHCHECKS_DENY_TOOLS": "<value>", "HEALTHCHECKS_INSECURE_TLS": "<value>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:HEALTHCHECKS_API_KEY, HEALTHCHECKS_URL, HEALTHCHECKS_READ_ONLY, HEALTHCHECKS_ALLOW_TOOLS, HEALTHCHECKS_DENY_TOOLS, HEALTHCHECKS_INSECURE_TLS。
Healthchecks 透過 stdio 在本機執行。
上次檢查時間:2026-11-10。 Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed