Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics
{ "mcpServers": { "io.github.oaslananka-health-monitor-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "HEALTH_MONITOR_DB": "<value>", "HEALTH_MONITOR_AUTO_CHECK": "<value>", "HEALTH_MONITOR_RETENTION_DAYS": "<value>", "HEALTH_MONITOR_MAX_CONCURRENCY": "<value>", "GITHUB_TOKEN": "<secret>", "GITLAB_TOKEN": "<secret>", "HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST": "<value>", "HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST": "<value>" } } }}Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
HEALTH_MONITOR_DB=<value> HEALTH_MONITOR_AUTO_CHECK=<value> HEALTH_MONITOR_RETENTION_DAYS=<value> HEALTH_MONITOR_MAX_CONCURRENCY=<value> GITHUB_TOKEN=<secret> GITLAB_TOKEN=<secret> HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST=<value> HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST=<value> claude mcp add io.github.oaslananka-health-monitor-mcp -- npx -y health-monitor-mcp@1.4.0Run in a terminal.
{ "mcpServers": { "io.github.oaslananka-health-monitor-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "HEALTH_MONITOR_DB": "<value>", "HEALTH_MONITOR_AUTO_CHECK": "<value>", "HEALTH_MONITOR_RETENTION_DAYS": "<value>", "HEALTH_MONITOR_MAX_CONCURRENCY": "<value>", "GITHUB_TOKEN": "<secret>", "GITLAB_TOKEN": "<secret>", "HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST": "<value>", "HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: HEALTH_MONITOR_DB, HEALTH_MONITOR_AUTO_CHECK, HEALTH_MONITOR_RETENTION_DAYS, HEALTH_MONITOR_MAX_CONCURRENCY, GITHUB_TOKEN, GITLAB_TOKEN, HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST, HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST.
MCP Health Monitor runs locally over stdio.
Last checked 2026-10-26. Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics
From the publisher
README is not crawled yet. Open the repository