INDIVIDUAL MCP TOOL

get_status_page

One status page: name, public URL, enabled, and its components with each linked monitor's current state.

uptimepage.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.uptimepage.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_status_page and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name or description suggests retrieving external content.

Parent server

uptimepage.dev

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.uptimepage]
url = "https://mcp.uptimepage.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "uptimepage": {
      "type": "http",
      "url": "https://mcp.uptimepage.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: uptimepage
Remote MCP URL: https://mcp.uptimepage.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "uptimepage": {
      "url": "https://mcp.uptimepage.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "uptimepage": {
      "type": "http",
      "url": "https://mcp.uptimepage.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "uptimepage",
  "transport": "streamable-http",
  "url": "https://mcp.uptimepage.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

get_flow_runs — A browser flow monitor's recent runs over a window (1h/24h/7d/30d): every declared step with its outcome and duration, the step a failure stopped on, and the page the browser saw.
get_flow_step_trend — How long each step of a browser flow monitor takes over a window (1h/24h/7d/30d), and how far it has moved: per step the earliest and latest mean duration, their ratio, and how many runs passed or failed it.
get_incident — One incident: affected monitor, severity, open/resolved times, error sample, and the full operator-update timeline.
get_incident_metrics — Incident metrics over a trailing window (default 30 days): MTTA/MTTR in seconds, total incidents, counts by severity and state, auto- vs human-resolved, and the noisiest monitors.
get_monitor — One monitor's full configuration — everything the check asserts (expected status, body match, headers, timeout, redirect and TLS policy), the regions it probes from, and how it alerts (failing checks before it pages, whether recovery is announced, the reminder interval, the multi-region quorum, and the ids of the channels it notifies) — with its current state, last error, and 24h/30d uptime.
get_monitor_history — One monitor's history over a window (1h/24h/7d/30d): uptime, latency series, a per-region split of the same window, failures with error text, and incident windows.
get_org_health — Org health summary: per-state monitor totals and the worst currently-failing monitors.
get_org_usage — Which org this connector is bound to, and the account's resource usage against plan limits: monitors, status pages, members, components, and key policy values.