Server data from the Official MCP Registry
Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status
Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status
Valid MCP server (3 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
5 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: HEALTH_MONITOR_DB
Environment variable: HEALTH_MONITOR_AUTO_CHECK
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-oaslananka-mcp-health-monitor": {
"env": {
"HEALTH_MONITOR_DB": "your-health-monitor-db-here",
"HEALTH_MONITOR_AUTO_CHECK": "your-health-monitor-auto-check-here"
},
"args": [
"-y",
"mcp-health-monitor"
],
"command": "npx"
}
}
}From the project's GitHub README.
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=1GET /health.env.exampleThe DB uses WAL mode on file-backed databases and applies schema migrations automatically on startup.
Build and run:
docker build -t mcp-health-monitor .
docker run --rm -p 3000:3000 -e HEALTH_MONITOR_AUTO_CHECK=1 mcp-health-monitor
Then check:
curl http://localhost:3000/health
npm install
npm run build
npm test
npm run test:integration
npm run lint
npm run lint:test
npm run format:check
Use npx --yes -p node@20.19.0 -p npm@10.8.2 npm <command> on workstations where the default
Node runtime is newer than the project target.
High-level module map:
src/app.ts: MCP tool registration and response formattingsrc/checker.ts: Live MCP connectivity probes with retry/backoffsrc/registry.ts: SQLite read/write paths for servers, checks, and pipeline recordssrc/db.ts + src/migrations.ts: Connection setup and schema upgradessrc/server-http.ts + src/mcp.ts: HTTP and stdio entrypointssrc/scheduler.ts: Optional background auto-check loopMore detail lives in architecture.md.
Detailed milestone planning lives in ROADMAP.md.
Read SECURITY.md for vulnerability reporting and docs/security.md for implementation-specific storage details.
See contributing.md for setup, standards, and PR expectations.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.