Uptimepage MCP server
{
"mcpServers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"mcpServers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"mcpServers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"servers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}{
"mcpServers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
The Uptimepage MCP server exposes monitoring and status page management capabilities from an Uptimepage organization. It lets you query monitor status, incident data, and manage status pages and alerts through an MCP interface, integrated with uptime monitoring that tracks HTTP, TCP, ICMP, DNS, TLS certificates, domains, and browser login flows.
- Query current monitor status and recent check results across your infrastructure.
- Retrieve active incidents and their public phases to incorporate into incident workflows.
- Programmatically create or update status page components and post incident updates via an LLM client.
Tools this server exposes
| Tool | Does |
|---|---|
| list_monitors | Retrieve all monitors in the organization with their current status. |
| get_monitor_status | Get detailed status and recent check results for a specific monitor. |
| list_incidents | Retrieve active and recent incidents for the organization. |
| list_status_pages | Retrieve all public status pages in the organization. |
| get_status_page_components | List components displayed on a specific status page. |
| create_incident | Create a new incident with an internal state and public phase. |
| update_incident | Update incident state, public phase, or narration text. |
| publish_status_update | Post an update to a status page incident. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.