
Mcp Server Health Monitor
Auto-discovers MCP servers from your Claude Desktop, Cursor, or VS Code configs and probes them by calling list_tools, the same handshake your agent uses. Unlike HTTP uptime monitors that just ping a port, this verifies the server actually speaks MCP and tracks tool schema drift across versions. Stores latency history in local SQLite with p50/p95 percentiles, generates self-contained HTML dashboards with uptime sparklines, and flags degraded servers based on response time thresholds. Runs as a daemon for continuous polling or on-demand via eight tools covering health checks, history queries, manual server registration, and update detection. Reach for this when you need protocol-aware monitoring without shipping data to external services.
- tools
- 8
- auth
- Secret needed
- transport
- STDIO
- env var
- 1
- last updated
- Nov 4, 2026
Tools
8 toolsPublic tool metadata for what this MCP can expose to an agent.
health_check_allProbes all configured servers in parallel via list_tools, measures latency, and stores results.
Probes all configured servers in parallel via list_tools, measures latency, and stores results.
No parameter schema in public metadata yet.
get_server_statusReturns per-server detail including latency, last seen time, 24-hour error count, last error message, and p50/p95 latency percentiles.
Returns per-server detail including latency, last seen time, 24-hour error count, last error message, and p50/p95 latency percentiles.
No parameter schema in public metadata yet.
list_degradedFilters to servers that are offline or have latency above the threshold.
Filters to servers that are offline or have latency above the threshold.
No parameter schema in public metadata yet.
get_historyReturns raw health check history for a specific server, ordered most-recent first.
Returns raw health check history for a specific server, ordered most-recent first.
No parameter schema in public metadata yet.
configure_serverRegisters a new MCP server to monitor.
Registers a new MCP server to monitor.
No parameter schema in public metadata yet.
remove_serverRemoves a manually registered server from monitoring.
Removes a manually registered server from monitoring.
No parameter schema in public metadata yet.
check_updatesDetects version drift by hashing tool schemas on each probe and comparing against the last stored hash.
Detects version drift by hashing tool schemas on each probe and comparing against the last stored hash.
No parameter schema in public metadata yet.
export_dashboardGenerates a self-contained single-file HTML dashboard with summary cards, per-server status table with p50/p95 latency, and inline SVG uptime sparklines.
Generates a self-contained single-file HTML dashboard with summary cards, per-server status table with p50/p95 latency, and inline SVG uptime sparklines.
No parameter schema in public metadata yet.
Sponsors
Configuration
YOUR_API_KEY*secretYour API key for the service
Readme
MCP Server Health Monitor
npm mcp-server-health-monitor package
MCP-native health monitoring that speaks the protocol, not just HTTP. Instead of pinging a port, it calls list_tools on each server — the same handshake your agent uses — so a green status means the server is actually ready to serve MCP requests. All health history stays local in SQLite; no external monitoring service required.
Tool reference | Configuration | Contributing | Troubleshooting
Key features
Details
- Repository
- github.com/dbsectrainer/mcp-server-health-monitor
- Category
- Monitoring & Observability
- Package
mcp-server-health-monitor- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active