UpHeron
OnlineNewUptime and vulnerability monitoring: check sites, manage monitors, incidents and status pages.
What it can do: 59 tools
check_websiteread-onlyChecks whether a public website responds right now, from the monitoring service, without an account. Returns status, HTTP code and timings. Free; limited to a few checks a minute.get_accountread-onlyPlan and its monitor slots (standard in plan_monitors, premium in premium_monitors with their kinds), and the workspace's time zone (workspace.time_zone), which report days follow. Call this first to know whether the plalist_locationsread-onlyLocation codes you can pass in a monitor's `locations`.list_monitorsread-onlyEvery monitor with its current status (pending, up, down, degraded), and interval. Free.get_monitorread-onlyOne 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, rget_monitor_resultsread-onlyA monitor's most recent check results, newest first. Older results may be merged: repeats checks with the same outcome up to last_checked_at. Free.get_uptime_historyread-onlyA monitor's daily uptime, kept for as long as it exists: checks, successful, failed and average response time per UTC day, oldest first. By default from the first check to today. Free.get_sla_reportread-onlyBusiness 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 theget_error_budgetsread-onlyEvery monitor with an availability objective (slo_target over slo_window_days, set with update_monitor): its availability over the rolling window, the error budget in seconds, how much is used and left, the last hour's blist_incidentsread-onlyOutages, newest first, with their status (open, acknowledged, resolved). Free.acknowledge_incidentMarks an open incident as being handled: its repeat alerts and escalation stop. Everyone alerted still hears when it recovers. Free.list_escalation_policiesread-onlyBusiness plans: escalation policies, whose id a monitor's escalation_policy_id takes, and their steps. Free.list_on_call_schedulesread-onlyBusiness plans: on-call schedules with who is on call now, until when, and who is next. Free.get_incidentread-onlyOne 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. Free.post_incident_updatePublishes an update on every published status page that shows the incident's monitor and in their RSS and Atom feeds, and on Pro plans emails those pages' subscribers. States: investigating, identified, monitoring, resolcomment_on_incidentAdds a comment to the incident's timeline, seen only by the workspace (Pro plans). Use it to record what you found or did. Free.open_incidentOpens an incident for what the checks cannot see: a slow service, a problem a customer reported. With a message it publishes the first update on the status pages that show its monitors (and emails their subscribers on Prupdate_incidentChanges the title status pages show (public_title) or the root cause (Pro plans) of any incident, and the title, severity and monitors of one opened by hand. Fields left out keep their value. Free.resolve_incidentResolves an incident opened with open_incident; the contacts it alerted hear so. A message is published as the last update on its status pages. Incidents opened by checks resolve with their checks. Free.write_postmortemWrites a resolved incident's post-mortem: summary, impact, root cause and follow-ups (one per line), on Pro plans. It stays in the workspace until published: true shows it under the incident on the status pages that showlist_status_pagesread-onlyThe workspace's status pages: their address (/status/{slug}), the monitors they show with the names visitors see, and their named groups of monitors in order. Free.update_status_page_componentsReplaces the monitors a status page shows, in order, each optionally in a named group ("API", "EU region"); a group sits where its first monitor is and shows their worst state. Every plan. Free.create_on_call_scheduleBusiness plans: a rotation through notification contacts (list_notification_contacts), handing off daily or weekly at a time in a time zone. The first member is on call from now. Free.update_on_call_scheduleBusiness plans. Fields left out keep their value; changing the members, rotation, handoff or time zone starts the rotation over. Free.delete_on_call_scheduleDeletes a schedule no escalation policy uses. Free.add_on_call_overrideBusiness plans: puts a contact on call in a schedule from starts_at to ends_at (up to 90 days), instead of the rotation. Overrides may not overlap. Free.remove_on_call_overrideRemoves an override from a schedule (its id is in the schedule's overrides). Free.create_escalation_policyBusiness plans: ordered steps, each alerting contacts and whoever is on call in schedules, then waiting for an acknowledgement before the next. Monitors use it with update_monitor's escalation_policy_id. Free.update_escalation_policyBusiness plans. Fields left out keep their value; steps replaces them all. Free.delete_escalation_policyDeletes a policy; its monitors go back to alerting their own contacts. Free.list_maintenance_windowsread-onlyMaintenance windows, latest first: times when failures open no incidents and send no alerts, for one monitor or all. A repeating window has its recurrence in words (repeats), its next occurrences and the ones skipped orcreate_maintenance_windowSchedules maintenance for one monitor or all: no incidents or alerts while it lasts (suppress_alerts), and with announce the status pages that show it list it and tell their subscribers. With recurrence it repeats daily,update_maintenance_windowChanges a maintenance window or every occurrence of a repeating one. Fields left out keep their value; recurrence null makes it a single window. Changing the times or recurrence undoes skipped and moved occurrences. Freechange_maintenance_occurrenceSkips (skipped: true), moves (starts_at and ends_at) or changes the message of one occurrence of a repeating maintenance window, leaving the others as they are; restore: true undoes it. Free.delete_maintenance_windowDeletes a maintenance window, every occurrence of a repeating one included. Subscribers told about an occurrence that has not started hear it is cancelled. Free.get_audit_logread-onlyWho changed what in the workspace, newest first: people, API tokens and agents, with the changed fields and IP (Business plan). Filter by resource_type (monitor, alert_channel, status_page, member, api_token…), action (mcreate_monitorCreates a monitor in a free slot of the workspace's plan. Premium monitors (multi-step transactions and code repositories) have slots of their own, on Pro and Business only. When every slot is in use the call fails withpreview_monitor_importread-onlyReads the monitors of another service: UptimeRobot (a read-only API key, or its bulk upload CSV), Better Stack (a team-based API token), Uptime Kuma (its JSON backup) or a CSV file in UpHeron's format (https://upheron.coimport_monitorsCreates the monitors the user chose from preview_monitor_import (send their `monitor` objects). Each takes a plan slot like create_monitor; ones already monitored are skipped. Imported heartbeats get new URLs, returned oupdate_monitorChanges a monitor's settings, within the plan's interval and location limits. Free.
…and 19 more.
Connect it
claude mcp add --transport http upheron https://upheron.com/mcpSettings → Connectors → Add custom connector
URL: https://upheron.com/mcp{
"mcpServers": {
"upheron": {
"url": "https://upheron.com/mcp"
}
}
}{
"servers": {
"upheron": {
"type": "http",
"url": "https://upheron.com/mcp"
}
}
}Questions
What does UpHeron do?
Uptime and vulnerability monitoring: check sites, manage monitors, incidents and status pages. It exposes 59 tools to AI assistants.
What tools does UpHeron provide?
59 tools, including check_website, get_account, list_locations, list_monitors, get_monitor, get_monitor_results, get_uptime_history, get_sla_report, get_error_budgets, list_incidents, acknowledge_incident, list_escalation_policies….
How do I connect UpHeron to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://upheron.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does UpHeron require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is UpHeron online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes UpHeron?
upheron.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Cloud & DevOps
-
CloudflareOnlineOfficialPopular
Cloudflare MCP servers
-
Google ComputeOnlineOfficialPopular
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
-
Google ContainerOnlineOfficialPopular
Provides read access to your GKE and Kubernetes resources.
-
Google ComposerOnlineOfficialPopular
Interact with your Google Cloud Composer resources using natural language commands.
-
Google BigtableadminOnlineOfficialPopular
Interact with your Google Bigtable resources using natural language commands.
-
Google DatastreamOnlineOfficialPopular
Interact with your Google Cloud Datastream resources using natural language commands.