Uptimepage
warningsmcp.uptimepage.dev
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.
https://mcp.uptimepage.dev/mcpWebsiteOAuthMCP 2025-11-25v1.5.0last checked 21 Oct 2026spoke MCP on 100% of 85 checks (30 days)initialize in 181 msLast checked 21 Oct 2026
- ✓Answered the MCP handshake (MCP 2025-11-25)
- ✓Auth detected: OAuth
- ✓Lists 39 tools
- !1 warning
- ✓Spoke MCP on 85 of 85 checks (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects
The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.
claude mcp add --transport http uptimepage https://mcp.uptimepage.dev/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects
The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.
Settings → Connectors → Add custom connector, then paste https://mcp.uptimepage.dev/mcp.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://mcp.uptimepage.dev/mcp.
ChatGPT docs · read on 2026-08-30
✓CursorConnects
The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.
{
"mcpServers": {
"uptimepage": {
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects
The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.
{
"servers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 21 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://app.uptimepage.dev |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | targets:read, status_page:read, incidents:read, maintenance:read, channels:read, targets:write, targets:execute, maintenance:write, maintenance:delete, incidents:write, status_page:write, variables:read |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 39 tools listable |
| Credentials demanded in prose | ✕create_monitor These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
What the probe found
1 of the 39 tools listed anonymously say in their own descriptions that they need an account or a key (create_monitor), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: acknowledge_incident, add_status_page_components, cancel_maintenance, create_maintenance, create_monitor, create_monitors, create_status_page, get_flow_runs, get_flow_step_trend, get_incident, get_incident_metrics, get_maintenance, get_monitor, get_monitor_history, get_org_health, get_org_usage, get_status_page, list_incidents, list_maintenance, list_monitors, list_notification_channels, list_regions, list_status_page_viewers, list_status_pages, list_tags, list_variables, pause_monitor, post_incident_update, post_maintenance_update, publish_incident, resolve_incident, resume_monitor, run_check_now, set_monitor_state, unpublish_incident, update_maintenance, update_monitor, update_status_page, update_status_page_component.
Tools
Contract history
Breaking: create_status_page, get_status_page, update_status_page
Instructions rewritten: list_status_page_viewers. The description an agent follows changed; the callable contract may not have.
Breaking: create_monitor, create_monitors
Breaking: create_status_page, get_status_page, update_status_page
Instructions rewritten: create_status_page, update_status_page. The description an agent follows changed; the callable contract may not have.
Breaking: create_monitor, create_monitors
Breaking: create_monitor, create_monitors
Breaking: create_monitor, create_monitors, get_monitor
Instructions rewritten: create_monitor. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: pause_monitor. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: get_incident, publish_incident. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: get_org_usage. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: list_regions. The description an agent follows changed; the callable contract may not have.
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchOwn this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/uptimepage)