health-monitor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address (for HTTP deployment) | 127.0.0.1 |
| GITHUB_TOKEN | No | Optional GitHub Actions read token | |
| GITLAB_TOKEN | No | Optional GitLab project/pipeline/job read token | |
| HEALTH_MONITOR_DB | No | SQLite database path | ~/.mcp-health-monitor/health.db |
| HEALTH_MONITOR_AUTO_CHECK | No | Enable scheduled checks with 1 | 0 |
| HEALTH_MONITOR_HTTP_TOKEN | No | Bearer token for POST /mcp | |
| HEALTH_MONITOR_ALLOW_STDIO | No | Allow trusted local stdio checks | 0 |
| HEALTH_MONITOR_RETENTION_DAYS | No | Health-history retention | 30 |
| HEALTH_MONITOR_MAX_CONCURRENCY | No | Scheduled and interactive check concurrency | 5 |
| HEALTH_MONITOR_STDIO_ALLOWLIST | No | Optional comma-separated executable allowlist | |
| HEALTH_MONITOR_HTTP_MAX_SESSIONS | No | Stateful session cap | 100 |
| HEALTH_MONITOR_HTTP_MAX_BODY_BYTES | No | Maximum inbound MCP body | 1048576 |
| HEALTH_MONITOR_HTTP_SESSION_TTL_MS | No | Stateful session TTL | 1800000 |
| HEALTH_MONITOR_HTTP_BODY_TIMEOUT_MS | No | Inbound body read timeout | 15000 |
| HEALTH_MONITOR_HTTP_ORIGIN_ALLOWLIST | No | Allowed remote client origins | |
| HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST | No | Private HTTP(S) origins allowed in full profile | |
| HEALTH_MONITOR_HTTP_STATEFUL_SESSIONS | No | Enable stateful Streamable HTTP sessions | 0 |
| HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST | No | Allowed self-hosted GitLab HTTPS origins |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| register_github_actionsA | Register a GitHub Actions workflow by owner, repository, and workflow file or ID. Only the token environment-variable name is stored; token values remain in the runtime environment. |
| check_github_actionsA | Check the latest run for a registered GitHub Actions workflow and return failed job and step diagnostics. |
| list_github_actionsA | List registered GitHub Actions workflow targets and their latest status. |
| unregister_github_actionsA | Remove a GitHub Actions workflow target and its stored check history. |
| register_gitlab_pipelineA | Register a GitLab CI/CD project pipeline. GitLab.com is allowed by default; self-hosted HTTPS origins require HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST. Only the token environment-variable name is stored. |
| check_gitlab_pipelineA | Check the latest registered GitLab pipeline and return failed job, stage, ref, commit, URL, and bounded trace diagnostics. |
| list_gitlab_pipelinesB | List registered GitLab pipeline targets and their latest status. |
| unregister_gitlab_pipelineA | Remove a GitLab pipeline target and its stored check history. |
| register_http_targetA | Register a GET-only HTTP or HTTPS endpoint with status, header, body, JSON, and TLS-expiry assertions. Public networks are allowed by default; private origins require full profile and HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST. |
| check_http_targetA | Check a registered HTTP target with DNS-pinned SSRF protection, bounded redirects/body reads, response assertions, and TLS-expiry diagnostics. |
| list_http_targetsA | List registered HTTP targets and their latest status, response, and TLS summary. |
| unregister_http_targetA | Remove an HTTP target and its stored check history. |
| register_serverA | Register an MCP server. Use http for a Streamable HTTP MCP endpoint, sse only for legacy Server-Sent Events servers, and stdio only for a local executable explicitly allowed by runtime policy. |
| check_serverA | Check the health of a registered MCP server, list tools, and measure response time. |
| check_allA | Check all registered MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets with one bounded concurrency limit. Results preserve MCP-then-GitHub-then-GitLab-then-HTTP registration order; optional tags filter all target kinds. |
| get_uptimeB | Get uptime history and statistics for a registered MCP server. |
| get_dashboardA | Get a dashboard overview of registered MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets with uptime and performance stats. |
| get_reportA | Get a human-readable Markdown health report for MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets. Paste directly into chat or docs. |
| list_serversB | List all registered MCP servers with their current status. |
| unregister_serverB | Remove a server from monitoring. |
| get_monitor_statsA | Get statistics about the health monitor itself, including database activity. |
| set_alertA | Configure alert thresholds for response time, uptime, and consecutive failures. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/oaslananka/health-monitor-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server