← Registry

DevOps

upheron.com

Monitors website uptime and performance, reporting status, incidents, locations, and route traces from a monitoring service.

1 endpoint59 known toolsFirst detected November 12, 2026Last detected November 12, 2026

ENDPOINT 1

https://upheron.com/mcp

No auth detected

MCP server metadata

Name
upheron
Version
1.2.0
Capabilities
toolsresources
Server instructions

UpHeron monitors websites, APIs, certificates, DNS and mail servers from several locations. - Reading (list_monitors, get_monitor, get_uptime_history, list_incidents, get_incident, check_website) is free. - During an outage, post_incident_update tells the visitors of the status pages that show the monitor (and their email subscribers) what is going on; comment_on_incident records notes for the team. For a problem the checks cannot see, open_incident opens one by hand and resolve_incident closes it. - Before create_monitor, call get_account: a workspace has as many monitors as its plan's slots. Premium monitors (micro_transaction, transaction, extended_transaction, repository) have slots of their own, on Pro and Business only. With every slot in use, the user upgrades at https://upheron.com/pricing. - Pass idempotency_key to create_monitor so a retry never creates a second monitor. - To bring monitors over from UptimeRobot, Better Stack, Uptime Kuma or a CSV file, call preview_monitor_import, show the user what would be created and skipped, then import_monitors with the ones they choose. - WebSocket and gRPC checks (websocket, grpc) come with Pro and Business; get_account says so in service_checks. On a smaller plan a monitor's plan_hold says what the plan paused: the monitor itself (paused), or its faster interval_seconds and extra locations; a bigger plan restores them. - A monitor down for weeks has long_outage: stops_at (its checks stop then if it is still down; the workspace's contacts were emailed) or stopped_at (UpHeron paused it after 30 days down). Resuming it counts again from then. Nobody opening the workspace in the dashboard after the warning gets it deleted instead. - To watch a code repository for vulnerable dependencies, create_monitor with kind "repository" and the GitHub or GitLab URL; a private repository needs check_options.token and the Pro plan. - On every plan, http and api monitors can alert on vulnerabilities in the website's software (vulnerability_alerts), checked daily and within 15 minutes of a new advisory on every plan; the website is scanned for its software weekly on Free and daily on Pro and Business. On Pro and Business, if you know or can read what the server runs, send it with import_software, or link the website's GitHub or GitLab repository with repository_url (and repository_token if private) for its exact dependency versions; read the findings with get_vulnerabilities. - Poll a monitor no faster than its interval_seconds. Docs: https://upheron.com/docs (also as Markdown at https://upheron.com/llms-full.txt).

Known tools 59

check_website

Checks whether a public website responds right now, from the monitoring service, without an account.

Inferred read-only
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.

Inferred read-only
list_locations

Location codes you can pass in a monitor's `locations`.

Inferred read-only
list_monitors

Every monitor with its current status (pending, up, down, degraded), and interval.

Inferred read-only
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).

Inferred read-only
get_monitor_results

A monitor's most recent check results, newest first.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
get_error_budgets

Every 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 burn rate and whether it burns fast, least budget left first.

Inferred read-only
list_incidents

Outages, newest first, with their status (open, acknowledged, resolved).

Inferred read-only
acknowledge_incident

Marks an open incident as being handled: its repeat alerts and escalation stop.

Inferred read-only
list_escalation_policies

Business plans: escalation policies, whose id a monitor's escalation_policy_id takes, and their steps.

Inferred read-only
list_on_call_schedules

Business plans: on-call schedules with who is on call now, until when, and who is next.

Inferred read-only
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.

Potential side effects
post_incident_update

Publishes 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.

Potential side effects
comment_on_incident

Adds a comment to the incident's timeline, seen only by the workspace (Pro plans).

Inferred read-only
open_incident

Opens an incident for what the checks cannot see: a slow service, a problem a customer reported.

Inferred read-only
update_incident

Changes 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.

Inferred read-only
resolve_incident

Resolves an incident opened with open_incident; the contacts it alerted hear so.

Inferred read-only
write_postmortem

Writes a resolved incident's post-mortem: summary, impact, root cause and follow-ups (one per line), on Pro plans.

Potential side effects
list_status_pages

The 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.

Inferred read-only
update_status_page_components

Replaces 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.

Inferred read-only
create_on_call_schedule

Business plans: a rotation through notification contacts (list_notification_contacts), handing off daily or weekly at a time in a time zone.

Inferred read-only
update_on_call_schedule

Business plans.

Inferred read-only
delete_on_call_schedule

Deletes a schedule no escalation policy uses.

Inferred read-only
add_on_call_override

Business plans: puts a contact on call in a schedule from starts_at to ends_at (up to 90 days), instead of the rotation.

Inferred read-only
remove_on_call_override

Removes an override from a schedule (its id is in the schedule's overrides).

Inferred read-only
create_escalation_policy

Business plans: ordered steps, each alerting contacts and whoever is on call in schedules, then waiting for an acknowledgement before the next.

Inferred read-only
update_escalation_policy

Business plans.

Inferred read-only
delete_escalation_policy

Deletes a policy; its monitors go back to alerting their own contacts.

Inferred read-only
list_maintenance_windows

Maintenance windows, latest first: times when failures open no incidents and send no alerts, for one monitor or all.

Potential side effects
create_maintenance_window

Schedules 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.

Inferred read-only
update_maintenance_window

Changes a maintenance window or every occurrence of a repeating one.

Inferred read-only
change_maintenance_occurrence

Skips (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.

Potential side effects
delete_maintenance_window

Deletes a maintenance window, every occurrence of a repeating one included.

Inferred read-only
get_audit_log

Who changed what in the workspace, newest first: people, API tokens and agents, with the changed fields and IP (Business plan).

Inferred read-only
create_monitor

Creates a monitor in a free slot of the workspace's plan.

Inferred read-only
preview_monitor_import

Reads 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.

Potential side effects
import_monitors

Creates the monitors the user chose from preview_monitor_import (send their `monitor` objects).

Potential side effects
update_monitor

Changes a monitor's settings, within the plan's interval and location limits.

Inferred read-only
pause_monitor

Stops checking a monitor.

Inferred read-only
resume_monitor

Starts checking a paused monitor again.

Inferred read-only
delete_monitor

Deletes a monitor and its history.

Inferred read-only
add_notification_contact

Adds an email address, chat channel, paging service, Jira project, webhook or phone number to alert on outages and recoveries.

Potential side effects
confirm_notification_contact

Confirms an sms or voice contact, added before they were retired, with the 6-digit code it was texted or told in a call.

Potential side effects
list_notification_contacts

Contacts that receive alerts, whether each is confirmed, and for phone contacts their latest text or call and whether it was delivered.

Inferred read-only
test_notification_contact

Sends a contact a test alert, at most 5 a minute for a workspace.

Inferred read-only
get_vulnerabilities

For an http or api monitor with vulnerability_alerts on: the vulnerabilities and unsupported releases found in the website's software, actively exploited and most severe first, with the version that fixes each, and the software they were matched on (found by scanning the website, imported, or added).

Inferred read-only
import_software

Tells the monitor what software the website and its server run, so their vulnerabilities are checked.

Inferred read-only
add_software

Adds one piece of software the website runs, by name (Debian, nginx, WordPress, Next.

Inferred read-only
remove_software

Removes an entry from get_vulnerabilities' software list.

Inferred read-only
mark_vulnerability_fixed

Records that the software behind a finding from get_vulnerabilities was upgraded: to `version`, or by default to the first version that fixes it (the finding's fix_version).

Inferred read-only
get_ports

For a monitor with port_scan on (Business plans): which of its host's addresses are verified and how to verify the rest (a file each address serves, or reverse DNS under the host with a TXT record), the ports the last weekly scan found open, flagged where the service usually should not be public, and the recent scans.

Inferred read-only
verify_host

Looks for the proof of each of the host's addresses from get_ports: the file served at the address, or its reverse DNS (PTR) under the host resolving back to it with the TXT record in place.

Inferred read-only
get_website_changes

For a website or API monitor: its security headers grade with what each missing or weak header does and how to fix it, its DNS records (A, AAAA, CNAME, NS, MX, SPF, DMARC) and the networks its addresses belong to, its page fingerprint (Business: title, external script hosts, and the latest change waiting to be accepted) and the recent header and DNS changes.

Inferred read-only
accept_page_change

Makes the page as it is now the new baseline of a monitor with content_watch, after get_website_changes shows a change you or the site's owner made on purpose.

Inferred read-only
scan_ports

Scans the verified host's common TCP ports now instead of waiting for the weekly scan, at most once an hour.

Inferred read-only
get_domain_watch

For an http or api monitor on Pro and Business plans: the website's registered domain, its subdomains from certificate transparency logs (crt.

Inferred read-only
scan_website_software

Scans the monitor's website for the software it runs and checks it against the vulnerability sources now, instead of waiting for the next scan.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for upheron.com was fetched 2026-11-13T18:52:38.713Z.

Trust status Neutral

upheron.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.