Endpoints: 76,849MCP servers: 32,723Payout addresses: 3,825Paid calls: 6,109Letters: 83Defects: 3,886counted 3 min ago
teppi

MCP servercom.upheron/upheron

Uptime and vulnerability monitoring: check sites, manage monitors, incidents and status pages.
UNRATEDActivestreamable-httpupheron.com

Overview

Score?
UNRATED 0.000
of what a free look can see, on 4 looks
Looks
4
last 2 hr ago
Tools
59

More info

URL
upheron.com/mcp
streamable-http
Says it is
upheron 1.2.0
protocol 2025-06-18
In the record since
5 days ago

Among servers32,723 with a card

0median 0.547 · this server 0.000 · highest on record 0.8351

Toolsfrom sha256:6b9c35d834…827f2b

The tools this server lists, read out of the definition it returned
ToolSchema
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
input · no output
acknowledge_incident
Marks an open incident as being handled: its repeat alerts and escalation stop. Everyone alerted still hears when it recovers. Free.
input · no output
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 t
input · no output
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.
input · no output
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
input · no output
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 undoe
input · no output
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.
input · no output
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.
input · no output
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 ow
input · no output
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'
input · no output
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 subscr
input · no output
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 e
input · no output
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. F
input · no output
delete_escalation_policy
Deletes a policy; its monitors go back to alerting their own contacts. Free.
input · no output
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.
input · no output
delete_monitor
Deletes a monitor and its history. Frees its plan slot.
input · no output
delete_on_call_schedule
Deletes a schedule no escalation policy uses. Free.
input · no output
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.
input · no output
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, sta
input · no output
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)
input · no output
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
input · no output
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 sub
input · no output
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 locatio
input · no output
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.
input · no output
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 w
input · no output
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
input · no output
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. F
input · no output
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, wit
input · no output
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
input · no output
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. Impo
input · no output
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.
input · no output
list_escalation_policies
Business plans: escalation policies, whose id a monitor's escalation_policy_id takes, and their steps. Free.
input · no output
list_incidents
Outages, newest first, with their status (open, acknowledged, resolved). Free.
input · no output
list_locations
Location codes you can pass in a monitor's `locations`.
input · no output
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 n
input · no output
list_monitors
Every monitor with its current status (pending, up, down, degraded), and interval. Free.
input · no output
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.
input · no output
list_on_call_schedules
Business plans: on-call schedules with who is on call now, until when, and who is next. Free.
input · no output
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.
input · no output
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 mo
input · no output
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 moni
input · no output
pause_monitor
Stops checking a monitor. Free.
input · no output
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: inve
input · no output
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
input · no output
remove_on_call_override
Removes an override from a schedule (its id is in the schedule's overrides). Free.
input · no output
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.
input · no output
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 w
input · no output
resume_monitor
Starts checking a paused monitor again. Free.
input · no output
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.
input · no output
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_
input · no output
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 cal
input · no output
update_escalation_policy
Business plans. Fields left out keep their value; steps replaces them all. Free.
input · no output
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 t
input · no output
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 un
input · no output
update_monitor
Changes a monitor's settings, within the plan's interval and location limits. Free.
input · no output
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.
input · no output
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. Eve
input · no output
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
input · no output
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 th
input · no output
Verify it yourselfnpx teppi-check https://upheron.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M79Q7H9Q1T4VPNF9SKMKP2AP