UpHeron
Check sites, manage monitors, incidents and status pages from an AI agent
Answered our latest tool-list check 16 hours ago with 59 tools. It will be marked verified after 3 successful checks in 7 days.
- Pricing
- Freemium
- Platforms
- Web, API
- Runs
- Remotely
- Version
- 1.2.0
- Listing updated
- 3 days ago
About UpHeron
UpHeron is a freemium MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
Only one tool, check_website, works without a token; every other call acts inside a workspace and respects its plan. You authenticate with an API token in the X-API-Key header or as a bearer token, where a read token suffices for status and a write token lets the agent create and change monitors. Clients that only support stdio can bridge with npx mcp-remote.
The tool list covers more than uptime. Agents can read uptime history and error budgets, open, acknowledge and resolve incidents, post status page updates, write post-mortems, schedule maintenance windows, manage on-call schedules and escalation policies, and import monitors from UptimeRobot, Better Stack, Uptime Kuma or a CSV. A vulnerability side tracks software found on a site, lets an agent import a lockfile or Dockerfile and marks findings fixed.
Tools carry read-only and destructive hints so clients can ask before changes. In Claude on the web and desktop, four tools also show interactive views. When a plan's monitor slots are full, create_monitor returns monitor_limit_reached. Free gives 20 monitors; Pro and Business are billed yearly.
Install
Run in a terminal
claude mcp add --transport http upheron https://upheron.com/mcpAdd to Settings → Connectors → Add custom connector
https://upheron.com/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"upheron": {
"url": "https://upheron.com/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"upheron": {
"type": "http",
"url": "https://upheron.com/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"upheron": {
"serverUrl": "https://upheron.com/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"upheron": {
"type": "http",
"url": "https://upheron.com/mcp"
}
}
}Tools this server provides (59)
Read directly from the server.
- 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 another monitor.
- 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 jitter over every round). Free.
- 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 monitor (lowest availability first) and overall. The dashboard and the API also give it as a PDF. Free.
- 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. Every plan. Free.
- 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.
- 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 page's visitors. Free.
- 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 pages the monitors' contacts once. It stays open until resolve_incident and never counts as downtime. Every plan, at most 20 open. Free.
- 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 feeds; false takes it off. Publish only when the user asks. Free.
- 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 days or monthly, in the workspace's time zone (get_account), starting with starts_at to ends_at. Every plan. Free.
- 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 prefix like monitor.), from and to (YYYY-MM-DD); pass next as before for older entries. Free.
- 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_reached: the user can upgrade at https://upheron.com/pricing or delete a monitor. Needs a write token.
- 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). Creates nothing: says which would be created and which skipped and why (no UpHeron check for it, already monitored, beyond the plan's monitors, needs Pro), with the
- 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: tell the user to point their scheduled jobs at them. Needs a write token. Free.
- 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 the user's own account with a provider, on every plan, which bills them: twilio (Account SID, Auth Token) and plivo (Auth ID, Auth Token) text or call, vonage (AP
- 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 (credentials, a trial account's unverified number, the sender).
- 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). Free.
- 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.txt, Pipfile.lock, poetry.lock, Gemfile.lock, go.mod, Cargo.lock, pom.xml, .csproj, Dockerfile, docker-compose.yml, .nvmrc, .bun-version, .tool-versions, mise.t
- 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 detected or imported entry for the same product. Free.
- 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 disappear, and one that still applies stays, marked with the version. Only records the version; it does not change the server. Free.
- 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. Free.
- 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 must stay in place, since every scan checks it again; only covered addresses are scanned. Free.
- 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. Settings are header_watch, dns_watch, d
- 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 reports no site there (subdomain_alerts), and the registered typo and look-alike spellings of the domain with their addresses, mail servers and registration dates (
- 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 it does
- Uptime and SLA data
- Reads uptime history, error budgets, and SLA reports on Business.
- Incident handling
- Opens, acknowledges, updates and resolves incidents and writes post-mortems.
- Status pages
- Posts updates and edits which monitors each page shows.
- On-call management
- Manages schedules, overrides and escalation policies on Business.
- Vulnerability tracking
- Finds vulnerable software and records fixes, with software imported from lockfiles.
- Monitor import
- Brings monitors from UptimeRobot, Better Stack, Uptime Kuma or CSV.
Good for
- Check whether a site is up right now without an account
- Ask an agent to add a monitor within plan slots
- Post an incident update to a status page
- Import monitors from another provider
- Scan a lockfile for vulnerable dependencies
Pricing
Freemium, from $4.9 a month
Free plan; Pro $4.90/mo and Business $9.90/mo billed yearly
Prices change. Check upheron.com before you buy.
UpHeron FAQ
Do I need a token?
Only check_website works without one; other tools need an API token.
What token type is needed to change monitors?
A write token; a read token is enough for status.
What does the free plan include?
20 monitors checked every 5 minutes, vulnerability alerts and 20 status pages.
What do paid plans cost?
Pro is $58.80 a year and Business $118.80 a year, billed yearly.
What happens when the plan is full?
create_monitor answers monitor_limit_reached with the tier and slots.
Is UpHeron free?
UpHeron has a free plan, with paid plans for more usage or features. Paid plans start at $4.9 a month.
How do I add UpHeron to Claude Code?
Run this command in your terminal: claude mcp add --transport http upheron https://upheron.com/mcp
What are the best alternatives to UpHeron?
The closest alternatives to UpHeron are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to UpHeron

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Ouroboros
MCP serverSpec-first layer that pins requirements and verifies results of AI coding agent work
Runs locally- Open source
- 6.4K GitHub stars
- Developer tools