Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

OpenStatus (BYOK) — connector documentation

  • MCP endpoint: https://byok-openstatus.connectorbay.com/mcp
  • REST API: POST https://byok-openstatus.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-openstatus.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own OpenStatus OpenStatus API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-openstatus.connectorbay.com/health · Tool schemas: https://byok-openstatus.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-openstatus · agent@connectorbay.com

What OpenStatus (BYOK) is for

OpenStatus (BYOK) lets an AI assistant read your own OpenStatus data through the OpenStatus API with a key you supply (OpenStatus API key). Read-only: 12 tools (list_http_monitors, list_tcp_monitors, get_monitor_status, get_monitor_summary, list_response_logs, list_status_pages, get_status_page_content, get_overall_status, list_status_reports, get_status_report, list_incidents, list_maintenances). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.openstatus.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenStatus. OpenStatus and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which of my OpenStatus HTTP monitors are failing?"
  • "Which TCP monitors do I have in OpenStatus?"
  • "Is OpenStatus monitor mon_123 healthy in every region?"
  • "What was the p95 latency of OpenStatus monitor mon_123 last week?"
  • "Show the latest checks of OpenStatus monitor mon_123"
  • "Which status pages do I run on OpenStatus?"

What it does

  • list_http_monitors: List the HTTP uptime monitors with name, check interval, timeout, regions, public flag and current status. Request headers, body and credentials of the monitor are not returned.
  • list_tcp_monitors: List the TCP port monitors with address, check interval, timeout, regions and current status.
  • get_monitor_status: Get the current status of one monitor in each region it runs from.
  • get_monitor_summary: Get aggregated metrics of one monitor over 1, 7 or 14 days: latency percentiles p50 to p99, counts of successful, degraded and failed checks, and the last check time.
  • list_response_logs: List recent check results of an HTTP monitor from the last 14 days: latency, status code, region, outcome and time.
  • list_status_pages: List your status pages with title, slug, custom domain and whether each is published.
  • get_status_page_content: Get a status page with its settings (not the access password), components, component groups, active status reports and scheduled maintenance. Give the page id or slug.
  • get_overall_status: Get the overall state of a status page (operational, degraded, partial outage, major outage or maintenance) and the state of each component. Give the page id or slug.
  • list_status_reports: List status reports (incident posts shown on status pages) with title, current stage, affected components and times. Use get_status_page_content for their update timeline.
  • get_status_report: Get one status report with its full update timeline (stage, message and time of every update).
  • list_incidents: List declared incidents, newest first, with title, severity, status and declared, started, resolved and closed times. Names of people involved are not returned.
  • list_maintenances: List scheduled maintenance windows with title, message, start and end and the status page components they cover.

BYOK key

You bring your own OpenStatus OpenStatus API key (https://www.openstatus.dev/tooling/api). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.openstatus.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the OpenStatus API (api.openstatus.dev) with a BYOK key; documentation: https://www.openstatus.dev/tooling/api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenStatus. OpenStatus and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your OpenStatus account.

Built for: Worldwide. Languages: English.