Openstatus

by openstatusHQ

Community Developer Tools 9k likes

OpenStatus's remote MCP server lets Claude, Cursor, or ChatGPT manage your status pages, monitors, and incidents by name: list pages, file a status report, resolve it, or schedule maintenance.

Add to Claude Code

claude mcp add --transport http openstatus https://api.openstatus.dev/mcp

Source: https://github.com/openstatusHQ/openstatus

About

OpenStatus is an open-source status-page-and-uptime-monitoring platform, and it exposes a hosted MCP server at api.openstatus.dev/mcp that sits alongside its REST API, CLI, Node SDK, and Terraform provider, all backed by the same API key, so anything the MCP server does shows up in the same audit log as if you'd used the dashboard. Through it, an agent can pull monitor status and response-log history, list your status pages and their components, and manage the incident lifecycle: creating a status report, posting updates to it, resolving it, or scheduling a maintenance window.

OpenStatus also has a complementary but separate MCP-related feature: monitoring-as-code checks specifically for other MCP servers. Instead of a plain HTTP health check, you define a JSON-RPC ping request in a version-controlled YAML file and OpenStatus fires it from multiple regions on a schedule, asserting on both the HTTP status and the exact JSON-RPC response, useful if you're the one operating an MCP server and want real uptime monitoring for it, not just a generic ping.

Key features

  • Remote MCP server (api.openstatus.dev/mcp) that shares auth and audit logging with OpenStatus's API, CLI, and SDKs
  • Read tools for monitor status, response logs, status pages, and page components
  • Incident-management tools: create, update, and resolve status reports; schedule maintenance windows
  • Separate monitoring-as-code support for JSON-RPC health checks against any MCP server you operate
  • Multi-region checks with configurable retry logic and check frequency
  • OTLP metrics export plus GitHub Actions integration for CI-driven monitoring

Use cases

  • Letting an on-call agent file and update a status report during an incident without opening the dashboard
  • Asking an agent for current monitor status and recent response-log history while triaging an alert
  • Scheduling a maintenance window ahead of a planned deploy straight from a chat client
  • Version-controlling health checks for your own MCP server's JSON-RPC endpoint alongside your other infra config

Available tools

get_monitor_status

Returns the current up/down status for a given monitor.

list_response_logs

Lists recent response-log entries for a monitor.

list_status_pages

Lists the status pages in your workspace.

create_status_report

Opens a new status report against one or more affected components.

resolve_status_report

Marks an open status report as resolved.

create_maintenance

Schedules a maintenance window on a status page.

Frequently asked questions

Does using the MCP server bypass OpenStatus's normal audit logging?

No. It uses the same API key and writes to the same audit log as the dashboard, REST API, and CLI.

Can OpenStatus monitor an MCP server I'm running myself?

Yes. Separately from the hosted MCP server above, OpenStatus supports defining JSON-RPC ping checks in a YAML config to monitor any MCP server's uptime and correctness from multiple regions.