health-checker
Implements a /health endpoint that returns JSON status indicating if the MCP server is operational. Developers and operators query it to confirm server availability before routing traffic or running tests. Applies to containerized deployments, load balancers, and monitoring integrations like Prometheus.
Overview
The health-checker MCP server provides a lightweight HTTP endpoint to report its own operational status. It responds to GET requests at /health with a JSON payload like {"status": "ok"} when healthy, or an error code if issues are detected. No authentication is required, enabling seamless integration into infrastructure monitoring.
Key Capabilities
- /health endpoint: Delivers immediate status check via simple HTTP GET. Returns 200 OK with JSON on success, or 5xx on failure, allowing scripted verification of server uptime and basic functionality.
No additional tools are exposed, focusing solely on self-health reporting for reliability in distributed systems.
Use Cases
-
Kubernetes Probes: Configure as liveness/readiness probe in pod specs to automatically restart unhealthy MCP server instances.
-
CI/CD Pipelines: Script checks in deployment workflows (e.g., GitHub Actions) to validate server readiness post-deploy before promoting to production.
-
Load Balancer Health Checks: Set as backend health gate in NGINX or AWS ALB to route traffic only to responsive servers.
-
External Monitoring: Poll endpoint with tools like Prometheus Blackbox Exporter or Uptime Kuma for alerting on downtime.
Who This Is For
DevOps engineers managing MCP server fleets, platform teams operating container orchestrators like Kubernetes/Docker Swarm, and backend developers embedding health gates in microservices architectures. Suited for any setup requiring automated uptime verification without complex dependencies.