POSTARD DEVELOPERS
Health checks and service status
The public Postard health page reports recent service checks without requiring an account or exposing private workspace data.
What is probed?
- REST API:
GET /healthmust identify the expected Postard process. - Backend:
GET /health/readychecks database access and a recent worker heartbeat. - MCP: OAuth resource metadata must identify the configured MCP URL, and an unauthenticated initialization must return the expected 401 challenge.
- Publishing worker: shown as online, offline, or intentionally disabled.
What does operational mean?
It means the listed probe responded as expected at its check time. It does not prove authorized MCP tool execution, Meta permissions, a specific post’s delivery, email delivery, billing, or historical uptime. A disabled worker is not presented as a live publishing service.
Refresh and failure behavior
The page renders useful HTML from the server and refreshes every minute while visible. Checks use short timeouts, parallel requests, a shared in-flight check, and a short snapshot cache. If refreshing fails, the previous check time remains visible with a stale-data notice. No latency or uptime figures are fabricated.
Security boundaries
Checks use only operator-configured origins, never a visitor-supplied URL. Public results contain component states and timings, without database addresses, tokens, account identifiers, or exception bodies. Private app routes and email preferences remain authenticated and excluded from indexing.