Service status
Verify live health at the service boundary.
This static page records published incidents and links to live machine-readable health. It does not pretend a build-time status is real-time monitoring.
API
Liveness shows that the process can respond. Readiness separately verifies required database and object-storage dependencies without revealing connection details.
Hosted MCP
Use protected-resource discovery and a capabilities connection test. Successful metadata alone does not prove an authenticated tool call.
Incident history
No public production incidents have been recorded in this documentation baseline. Future entries will include start, detection, mitigation, resolution, impact, and follow-up dates.
Reporting a problem
Include the affected component, UTC timestamp, request ID, and redacted error code. Never include credentials or private source content.
Incident communication
During a confirmed incident, GetMD publishes affected components, impact, start and update times, mitigations, and the next update deadline. Resolution is followed by a privacy-reviewed incident summary and owned corrective actions.