Connect Uptimepage and your agent gets 16 tools, among them get_flow_runs, get_flow_step_trend, get_incident. It answers at https://mcp.uptimepage.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Use this to answer why a login check failed. Read-only. Inputs: id, window |
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. Use this to spot a step drifting Inputs: id, window |
get_incident | One incident: affected monitor, severity, open/resolved times, error sample, and the full operator-update timeline. Read-only. Inputs: id |
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. Read-only. Inputs: window_days |
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 ann Inputs: id |
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. Pass `region` to narrow it to one probe region and tell a partial outage fro Inputs: id, region, window |
get_org_health | Org health summary: per-state monitor totals and the worst currently-failing monitors. The one-shot answer to 'what is broken right now?'. Read-only. |
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. Caps are pooled across every org the account owns, so the counts can exceed what |
get_status_page | One status page: name, public URL, enabled, and its components with each linked monitor's current state. Read-only. Inputs: slug |
list_incidents | List the org's incidents: incident id, affected monitor, severity, open/resolved times, and latest update phase. Defaults to currently-open ones; pass state="all" with an optional from/to window (default: last 30 days) for resolved history, Inputs: cursor, from, monitor_id, state, to |
list_monitors | List monitors with optional state/type/tag filters and cursor pagination. Each item carries its current state and last-checked time. Read-only. Inputs: cursor, state, tag, type |
list_notification_channels | The org's notification channels: id, operator-set name, kind (email, slack, telegram, webhook, and so on), and whether the channel is enabled. Two flags say a channel is not working even where it reads as ready: awaiting_verification for an |
list_regions | The fleet's probe regions: id, display name, city, country, continent, and whether each is on by default for a new monitor. Reports `max_regions` only when the plan reaches fewer regions than the catalog lists, so a set too large to be acce |
list_status_pages | List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only. Inputs: cursor |
list_tags | Every tag in use across the org's monitors, most-used first, with how many monitors carry each. Pass one back as the `tag` filter to list_monitors. Read-only. |
list_variables | The org's reusable variables: key, and whether it is a secret. Values are never returned, and a secret's value is never even read. Write a variable into a monitor's header or body as `{{ key }}`, which is resolved when the check runs: this |
Every block below points at https://mcp.uptimepage.dev/mcp. Pick your client and copy.
claude mcp add --transport http uptimepage https://mcp.uptimepage.dev/mcp
{
"mcpServers": {
"uptimepage": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.uptimepage.dev/mcp"]
}
}
}{
"mcpServers": {
"uptimepage": {
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"servers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"context_servers": {
"uptimepage": {
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"mcpServers": {
"uptimepage": {
"serverUrl": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"mcpServers": {
"uptimepage": {
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}name: Uptimepage
version: 0.0.1
schema: v1
mcpServers:
- name: Uptimepage
type: streamable-http
url: https://mcp.uptimepage.dev/mcp{
"mcpServers": {
"uptimepage": {
"httpUrl": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"mcpServers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"mcpServers": {
"uptimepage": {
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.uptimepage.dev%2Fmcp&type=streamable_http&id=uptimepage&name=Uptimepage
It answered our last check on 19 October 2026 in 532 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by uptimepage.dev and served from mcp.uptimepage.dev, the vendor's own domain: https://mcp.uptimepage.dev/mcp.
16, as returned by the server's own tools/list on 11 September 2026: get_flow_runs, get_flow_step_trend, get_incident, get_incident_metrics, get_monitor, get_monitor_history, get_org_health, get_org_usage, and 8 more.
It answered our last check on 19 October 2026 in 532 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.uptimepage.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.uptimepage. Endpoint host: mcp.uptimepage.dev. ARD identifier: urn:air:dev.uptimepage:mcp:uptimepage.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.