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

RealUptime (BYOK) — connector documentation

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

What RealUptime (BYOK) is for

RealUptime (BYOK) lets an AI assistant read your own RealUptime data through the RealUptime API with a key you supply (RealUptime API key (starts with ru_live_)). Read-only: 11 tools (list_checks, get_check_status, list_heartbeat_runs, list_heartbeats, query_check_results, list_status_pages, get_status_page, list_incidents, get_active_maintenance, list_error_projects, list_error_issues). 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 realuptime.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by RealUptime. RealUptime 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 monitors do I have in RealUptime?"
  • "Is my API monitor up right now in all regions?"
  • "Did my nightly backup heartbeat run succeed last night?"
  • "Which heartbeat monitors do I have?"
  • "What was the p95 latency of my monitors per hour yesterday?"
  • "Which status pages do I run on RealUptime?"

What it does

  • list_checks: List every monitor on the account (http, heartbeat, tcp, dns, smtp, ping, multistep) with name, URL or host, interval, selected probe regions, pause state and tags.
  • get_check_status: Get one monitor's current status (operational, degraded, down, stale or unknown) aggregated across its probe regions, with each region's state and last check time.
  • list_heartbeat_runs: List a heartbeat monitor's job runs, newest first: start and finish time, outcome (running, success, fail, superseded), duration, stuck flag and exit code. Only heartbeat monitors have runs.
  • list_heartbeats: List the account's heartbeat monitors (jobs that must ping in on a schedule), oldest first.
  • query_check_results: Query probe results over a time range for some or all monitors: raw rows (time, region, ok, status code, latency, error) or, with a step, downsampled buckets with sample counts and p50/p95 latency. Reads are clamped to the plan's history window.
  • list_status_pages: List the account's status pages with slug, name, custom domain and its verification state, branding fields and mirrored vendor components.
  • get_status_page: Get one status page by id: slug, name, custom domain and domain state, title, description and logo.
  • list_incidents: List incidents across all monitors, newest first: title, status, region(s) that failed and recovered, opened and resolved time and acknowledgement.
  • get_active_maintenance: Show the maintenance window that is active right now for one status page, or null if there is none.
  • list_error_projects: List the account's error-tracking projects with name, key hint and revoked flag, the plan's event quota and retention, and this period's usage.
  • list_error_issues: List error issues of one project filtered by text, release, status, last-seen window or tag, with a total and a truncation flag.

BYOK key

You bring your own RealUptime RealUptime API key (starts with ru_live_) (https://dashboard.realuptime.io/account/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 realuptime.io 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 RealUptime API (realuptime.io) with a BYOK key; documentation: https://docs.realuptime.io/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 RealUptime. RealUptime 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 RealUptime account.

Built for: Worldwide. Languages: English.