health-monitor-mcp
by oaslananka
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 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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