dev.uptimepage/uptimepage MCP server: daily status and tool changes

Answered initialize and tools/list on all 23 daily checks recorded in the last 30 days (2026-10-06 to 2026-10-28); 39 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; tool definitions last changed on 2026-10-24 after 2 days without change; no agent-reported interactions.

Does it respond?

Latest daily check: 2026-10-28: the server answered initialize and tools/list.

Observed days in the last 30: 23
Answered initialize and tools/list: 23
Required authentication: 0
No response: 0
Remotes differed: 0

Does it require authentication?

It did not return HTTP 401/403 on any of the 23 observed days. Lowdown checks without credentials.

Did its tools change recently?

Tool definitions changed on 9 of 22 compared days.

2026-10-24: input or output schemas changed
2026-10-22: input or output schemas changed
2026-10-21: server version changed
2026-10-18: input or output schemas changed, descriptions changed
2026-10-17: input or output schemas changed

What tools does it list?

39 tools on 2026-10-28:

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

MCP Registry declaration

Registry name: dev.uptimepage/uptimepage
Declared version: 1.0.0
Status: active
Declared hosts: mcp.uptimepage.dev