List your agent

UpHeron

MCP server● Hosted · onlinev1.2.0

Uptime and vulnerability monitoring: check sites, manage monitors, incidents and status pages

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: review pull requests.
All AI agents to review pull requests, ranked →

Similar tools

Listed for the same task: review pull requests

Reviews

No review yet. Used UpHeron? Be the first to help others choose.

What it does

UpHeron is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as review pull requests or scan code for vulnerabilities.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.2.0
PriceNot in the registry
First seen12 Nov 2026
Last checked18h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://upheron.com/mcp streamable-http

In Claude Code: claude mcp add --transport http upheron https://upheron.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "upheron": {
      "url": "https://upheron.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE UpHeron answered an MCP connection on 15 Nov 2026 and introduced itself as upheron 1.2.0 (MCP protocol 2025-06-18).

59 tools offered to AI assistants

  • check_website · Checks 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_account · Plan 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 plan has room for anoth
  • 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. Free.
  • 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 jitte
  • get_monitor_results · A 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_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. By default from the first check to today. Free.
  • 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
  • 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
  • list_incidents · Outages, newest first, with their status (open, acknowledged, resolved). Free.
  • acknowledge_incident · Marks an open incident as being handled: its repeat alerts and escalation stop. Everyone alerted still hears when it recovers. Free.
  • list_escalation_policies · Business plans: escalation policies, whose id a monitor's escalation_policy_id takes, and their steps. Free.
Show 47 more
  • list_on_call_schedules · Business plans: on-call schedules with who is on call now, until when, and who is next. Free.
  • 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. Free.
  • 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. States: investigating, identified, monitoring, resolved. Write for the p
  • comment_on_incident · Adds 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_incident · Opens 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 Pro plans); alert page
  • 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. Fields left out keep their value. Free.
  • resolve_incident · Resolves 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_postmortem · Writes 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 show it and in their fee
  • 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. Free.
  • 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. Every plan. Free.
  • 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. The first member is on call from now. Free.
  • update_on_call_schedule · Business plans. Fields left out keep their value; changing the members, rotation, handoff or time zone starts the rotation over. Free.
  • delete_on_call_schedule · Deletes a schedule no escalation policy uses. Free.
  • 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. Overrides may not overlap. Free.
  • remove_on_call_override · Removes an override from a schedule (its id is in the schedule's overrides). Free.
  • 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. Monitors use it with update_monitor's escalation_policy_id. Free.
  • update_escalation_policy · Business plans. Fields left out keep their value; steps replaces them all. Free.
  • delete_escalation_policy · Deletes a policy; its monitors go back to alerting their own contacts. Free.
  • list_maintenance_windows · Maintenance 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 or moved. Free.
  • 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. With recurrence it repeats daily, weekly on chosen da
  • update_maintenance_window · Changes 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. Free.
  • 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. Free.
  • delete_maintenance_window · Deletes 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_log · Who 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 (monitor.updated, or a
  • create_monitor · Creates 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 with monitor_limit_reache
  • 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.com/docs/import). Crea
  • import_monitors · Creates 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 once as heartbeat_url
  • update_monitor · Changes a monitor's settings, within the plan's interval and location limits. Free.
  • pause_monitor · Stops checking a monitor. Free.
  • resume_monitor · Starts checking a paused monitor again. Free.
  • delete_monitor · Deletes a monitor and its history. Frees its plan slot.
  • add_notification_contact · Adds an email address, chat channel, paging service, Jira project, webhook or phone number to alert on outages and recoveries. Email contacts must open a confirmation link before they receive alerts. A phone number texts or calls through th
  • 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. The code works for 24 hours and 5 tries. Ask the phone's owner for it; never guess.
  • 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.
  • test_notification_contact · Sends a contact a test alert, at most 5 a minute for a workspace. For a phone contact it is a real text or call through the user's account, which counts toward its 6 texts or 3 calls an hour; an error says in words what the provider refused
  • 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 ma
  • import_software · Tells the monitor what software the website and its server run, so their vulnerabilities are checked. Send a file's contents (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock, mix.lock, composer.json/.lock, requirements.
  • add_software · Adds one piece of software the website runs, by name (Debian, nginx, WordPress, Next.js…), package (npm:lodash, composer:vendor/package, pypi:django, wp-plugin:slug) or NVD product (cpe:vendor:product), with its version if known. Replaces a
  • remove_software · Removes an entry from get_vulnerabilities' software list. Software the scan found is ignored instead, so the next scan does not add it back. Free.
  • 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). The monitor is checked again; findings that no longer apply disapp
  • 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
  • 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. The TXT record alone proves no address. The proof
  • 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 (Busi
  • 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. Later looks compare with it. Free.
  • scan_ports · Scans the verified host's common TCP ports now instead of waiting for the weekly scan, at most once an hour. Takes a minute or two; then read get_ports. Free.
  • 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.sh, which can be days or weeks behind) with where each points and any CNAME to a service that repo
  • 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. Takes up to a minute; then read get_vulnerabilities. Free.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version1.2.0DECLAREDSRC-001 Official MCP Registry18h ago
Hosted endpointhttps://upheron.com/mcpDECLAREDSRC-001 Official MCP Registry18h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry18h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry18h ago
Websitehttps://upheron.com/docs/mcpDECLAREDSRC-001 Official MCP Registry18h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry18h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry18h ago

Change history

  • VERSION12 Nov 2026
    1.1.1 → 1.2.0
  • VERSION12 Nov 2026
    1.1.0 → 1.1.1
  • VERSION12 Nov 2026
    1.0.0 → 1.1.0
  • NEW12 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run UpHeron? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor UpHeronLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of UpHeron?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/upheron?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/upheron/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about UpHeron

How do I connect UpHeron?

Use the hosted endpoint https://upheron.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does UpHeron offer?

When Electra Index connected on 15 Nov 2026, it listed 59 tools: check_website, get_account, list_locations, list_monitors, get_monitor, get_monitor_results, get_uptime_history, get_sla_report and more. The full list is in "Live check" above.

Is UpHeron online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use UpHeron for?

Based on its description, it is most relevant to: review pull requests, scan code for vulnerabilities.