INDIVIDUAL MCP TOOL
get_incident
One incident with its timeline (detected, acknowledged, comments, status page updates, recovered), root cause and post-mortem, and the status pages its updates go to with their subscriber counts.
LIVE ENDPOINT
https://upheron.com/mcp
Connect to this endpoint to inspect the live schema for get_incident and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description contains a write-action term.
Parent server
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.upheron]
url = "https://upheron.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"upheron": {
"type": "http",
"url": "https://upheron.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: upheron
Remote MCP URL: https://upheron.com/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": {
"upheron": {
"url": "https://upheron.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"upheron": {
"type": "http",
"url": "https://upheron.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "upheron",
"transport": "streamable-http",
"url": "https://upheron.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
check_website— Checks whether a public website responds right now, from the monitoring service, without an account.get_account— Plan and its monitor slots (standard in plan_monitors, premium in premium_monitors with their kinds), and the workspace's time zone (workspace.list_locations— Location codes you can pass in a monitor's `locations`.list_monitors— Every monitor with its current status (pending, up, down, degraded), and interval.get_monitor— One monitor with uptime for 24 hours, 7 days and 30 days, its last 90 days, incident totals, its latest results with errors, recent incidents, and route traces from failing locations (Pro and Business: each hop's loss, round trips and jitter over every round).get_monitor_results— A monitor's most recent check results, newest first.get_uptime_history— A monitor's daily uptime, kept for as long as it exists: checks, successful, failed and average response time per UTC day, oldest first.get_sla_report— Business plans: availability against an SLA target for a range of days in the workspace's time zone (time_zone in get_account; by default this month), with the downtime budget used and left, incidents, MTTR, MTBF and the longest outage, per monitor (lowest availability first) and overall.