Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status
{
"mcpServers": {
"io-github-oaslananka-mcp-health-monitor": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
MCP Server for GCP environment for interacting with various Observability APIs.
MCP Server for kubernetes management commands
Model Context Protocol (MCP) server for Kubernetes and OpenShift
The power of Claude Code / GeminiCLI / CodexCLI + [Gemini / OpenAI / OpenRouter / Azure / Grok / Ollama / Custom Model / All Of The Above] working as one.
MCP Security Weekly
Get CVE alerts and security updates for io.github.oaslananka/mcp-health-monitor and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server health monitoring, uptime tracking, Azure DevOps pipeline status, and alert evaluation through natural-language tools.
mcp-health-monitor keeps a registry of the MCP servers you care about, performs real MCP
handshakes against them, records health history in SQLite, and reports uptime, latency, and
alert thresholds back through MCP tools. It also tracks Azure DevOps pipelines so app health
and delivery health can be checked from the same place.
Run the monitor over stdio:
npx -y mcp-health-monitor
Example Claude Desktop or VS Code MCP entry:
{
"name": "mcp-health-monitor",
"version": "1.0.2",
"mcpName": "io.github.oaslananka/mcp-health-monitor",
"description": "Monitor MCP server health, uptime, response times, and Azure DevOps pipelines",
"transport": "stdio",
"command": "npx",
"args": ["-y", "mcp-health-monitor"]
}
| Tool | Purpose | Typical prompt |
| ---- | ------- | -------------- |
| register_server | Save an MCP server to monitor | Register https://example.com/mcp as prod-gateway |
| check_server | Run a live health check for one server | Check prod-gateway now |
| check_all | Check all registered servers | Check all my MCP servers |
| get_uptime | Return uptime plus latency stats | Show 24h uptime for prod-gateway |
| get_dashboard | Return JSON dashboard data | Give me a 24h dashboard |
| get_report | Return a Markdown report | Generate a Markdown health report for 24h |
| list_servers | Show registered servers | List all monitored servers |
| unregister_server | Remove a server | Stop monitoring local-debugger |
| set_alert | Configure thresholds | Alert if prod-gateway exceeds 500ms or drops below 99% uptime |
| get_monitor_stats | Show monitor-level stats | How many checks has the monitor recorded? |
| register_azure_pipelines | Register Azure pipeline groups | Track CI and Publish pipelines for my repo |
| check_pipeline_status | Read latest Azure pipeline runs | Check pipeline status for my release group |
| get_pipeline_logs | Fetch Azure build logs | Show the failed logs for the latest Publish build |
| check_all_projects | Combine MCP and Azure health | Check all projects |
Register a pipeline group with an org, project, pipeline names, and a PAT:
register_azure_pipelines name="mcp-health-monitor" organization="oaslananka" project="open-source" pipeline_names=["mcp-health-monitor CI","mcp-health-monitor Publish"] pat_token="..."
PAT tokens are stored as base64 in the local SQLite database for v1.0. This is encoding, not encryption. See credential storage notes.
Use set_alert to configure one server:
| Field | Meaning |
| ----- | ------- |
| max_response_time_ms | Alert when a check exceeds this latency |
| min_uptime_percent | Alert when the selected uptime window drops below this value |
| consecutive_failures_before_alert | Alert after this many non-up results in a row |
Alerts are evaluated inline by check_server, check_all, and get_dashboard. Webhook delivery
is planned for v1.1, and no webhook MCP tool is shipped in v1.0.x.
~/.mcp-health-monitor/health.dbHEALTH_MONITOR_DB=/custom/path/health.dbHEALTH_MONITOR_AUTO_CHECK=1