hyperping
mcp remote · streamable-http · v1.0.0 · source: crawl
https://api.hyperping.io/v1/mcp
https://github.com/hyperping/mcp-server
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Works
100
Verified Oct 31, 2026 · p50 832 ms · p95 981 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'hyperping-monitors' |
| tools_listed | 15 | pass | 69 tools |
| schema_complete | 15 | pass | 67 of 69 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 832 ms |
| latency_p95 | 5 | pass | p95 981 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (69)
| Name | Description | Schema |
|---|---|---|
get_status_page | One status page with its settings (languages, subscriptions, access) and the services it shows, section by section, with their UUIDs and type (monitor, healthcheck, server or component). | typed |
list_recent_alerts | Alert notifications (up/down transitions) over a date range. Defaults to last 30 days. | typed |
list_monitors | Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring). | typed |
get_monitor | Fetch a single monitor by its UUID. | typed |
create_monitor | Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks. | incomplete |
get_integration | One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.). | typed |
list_status_pages | Status pages in the project, 20 per page: UUID, name, public URL, password protection. | typed |
update_monitor | Patch a monitor. Pass only fields you want to change; others are preserved. | incomplete |
pause_monitor | Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true. | typed |
resume_monitor | Resume a paused monitor. Same as update_monitor with paused=false. | typed |
search_monitors_by_name | Case-insensitive substring search across monitor names and URLs. | typed |
get_status_summary | Up/down/paused counts plus a list of currently down monitors with the timestamp they went down. | typed |
list_outages | Paginated list of outages in the project. Filter by status, type, or search term. | typed |
get_outage | Fetch a single outage by UUID, including acknowledgements, description, and root cause. | typed |
get_outage_timeline | Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution. | typed |
get_monitor_outages | Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages. | typed |
create_outage | Declare an incident by hand, for a problem no monitor detects. It appears under Incident Management in the dashboard and, with an escalation policy, pages its on-call responders. Internal: nothing is | typed |
acknowledge_outage | Mark an ongoing outage as being handled: repeat alerts stop. Escalation steps still fire on schedule; resolve it or fix the cause to stop them. | typed |
escalate_outage | Page the next step of the outage's escalation policy now instead of waiting for it. Each call moves one step further. | typed |
resolve_outage | Resolve an incident declared by hand or a server incident, and send the recovery to the channels it paged. An outage detected on a monitor resolves itself when its checks pass again. | typed |
get_monitor_uptime | Uptime percentage over a date window, aggregated and optionally per day/hour/week/month. | typed |
get_monitor_response_time | Response time latency trend over a date window. Returns a per-monitor breakdown — pass all monitors at once in monitor_uuids rather than calling this once per monitor. | typed |
get_monitor_mttr | Mean time to resolve (MTTR) per monitor over a date window, in seconds. Already per-monitor — pass all monitors at once in monitor_uuids rather than calling this once per monitor. | typed |
get_monitor_mtta | Mean time to acknowledge (MTTA) per monitor over a date window, in seconds. Already per-monitor — pass all monitors at once in monitor_uuids rather than calling this once per monitor. | typed |
get_monitor_anomalies | Anomaly-detection output for a single monitor (flapping, latency spikes, etc.). | typed |
get_monitor_http_logs | Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures. | typed |
list_on_call_schedules | All on-call schedules in the project. Each entry typically includes rotation config and current on-call. | typed |
get_on_call_schedule | One schedule by UUID with full rotation detail and the linked escalation policies. | typed |
list_escalation_policies | All escalation policies in the project. Use to find which monitors route alerts where. | typed |
get_escalation_policy | One policy by UUID. Reveals step sequence, linked schedules, and contact channels. | typed |
list_team_members | Users on the project, with names and emails. Use to resolve user IDs from schedules/policies. | typed |
get_on_call_now | Who is on call, per on-call schedule, right now or at the moment given in `at` (e.g. next Saturday 10:00), computed by the engine that pages people: names, emails and the rotation of each person, and | typed |
list_integrations | All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.). | typed |
create_status_page | Create a status page on a hyperping.app subdomain, with sections of monitors, healthchecks, components and servers. It is public as soon as it exists: confirm the name, address and services with the u | typed |
update_status_page | Change a status page's name, description, website, look or subscription button. Only the fields passed change. The page is public: confirm the change with the user first. | typed |
add_status_page_services | Show monitors, healthchecks, components or servers on a status page, in the section you name (created at the end if the page has none by that name) or the first one. Services already on the page stay | typed |
remove_status_page_services | Take monitors, healthchecks, components or servers off a status page, wherever they appear, groups included. Their settings on the page (display name, description) are lost. | typed |
list_status_page_incidents | Incidents published on status pages, newest first, each with its current stage and latest update. For downtime detected on monitors, use list_outages. | typed |
get_status_page_incident | One status page incident with every update (newest first, with their UUIDs), its status pages and affected components. | typed |
create_maintenance_window | Schedule a maintenance window: checks and alerts stop for its monitors during the window, and the status pages you pass announce it. Public once it has status pages: confirm with the user first. | typed |
create_status_page_incident | Publish an incident on status pages, with its first update. Public, and emailed to subscribers unless notify_subscribers is false: confirm the wording with the user first. To record an incident intern | typed |
add_status_page_incident_update | Post an update on a status page incident (investigating, identified, update, monitoring, resolved). Public, and sent to subscribers unless notify_subscribers is false. | typed |
resolve_status_page_incident | Close a status page incident with a final "resolved" update. Same as add_status_page_incident_update with status "resolved"; refuses an incident that is already resolved. | typed |
update_status_page_incident | Change a status page incident's title, type, status pages or affected services. The pages show the change right away; subscribers are not notified. To tell them something, post an update. | typed |
edit_status_page_incident_update | Correct the text or stage of an update already posted, e.g. a typo. The page shows the correction; subscribers are not notified again and its date is kept. | typed |
list_maintenance_windows | Maintenance windows, 20 per page, with their monitors, status pages, updates and status (upcoming, inprogress, completed). | typed |
get_maintenance_window | One maintenance window with its updates and the state of its subscriber notification. | typed |
update_maintenance_window | Reschedule a maintenance window, rename it, change its monitors or status pages, or post a public update on it. The pages show the change; subscribers are not notified. | typed |
complete_maintenance_window | End a maintenance window in progress now: checks and alerts resume on its monitors and the status pages show it as completed. | typed |
cancel_maintenance_window | Cancel a maintenance window that has not started: it is deleted and leaves the status pages. Subscribers already told about it are not told it is cancelled. To end one in progress, use complete_mainte | typed |
search_logs | Search the project's logs, newest first. Logs search language (not SQL): free words are ANDed (whole words), "exact phrase", -word to exclude, service:api, host:web-1, env:prod, source:src_…, level:er | typed |
get_outage_logs | Logs around one outage (incident) of the project: from 15 min before it started to 5 min after it ended. Returns warnings and errors grouped by message pattern, the latest matching lines, and a per-le | typed |
summarize_log_errors | Groups the project's errors (or warnings) of a time window by message pattern (numbers, ids and IPs normalized), most frequent first: count, share, trend (>1 = rising in the last quarter of the window | typed |
list_log_dashboards | Log dashboards of the project: name, tags, widget count, template, last update. With `uuid`, one dashboard in detail: its time range, variables, sections and every widget with its chart as HPL (run on | typed |
run_log_chart | Aggregates the project's logs into a chart and returns a compact summary: per series min/max/avg/last and up to `max_points` points, a table (up to 50 rows) or a single value. HPL = `<search> | <aggre | typed |
create_log_dashboard_from_template | Creates a log dashboard from a ready-made template (overview, errors-patterns, http-access, app-otel, containers, host-syslog, databases, jobs, ingestion-cost, incident-war-room, vercel). The template | typed |
get_outage_checks | Region-by-region evidence for one outage ("outage_…" or an incident key like "INC-12"): a verdict — "global" (every checked region failed), "partial" (some regions stayed healthy, listed), "single_reg | typed |
find_correlated_outages | Other incidents of this project that started within ±window_minutes (default 10, max 60) of an outage (outage_uuid, or incident key) or of a moment (at), each with monitor (uuid, name), start, end or | typed |
get_recent_changes | What changed on a monitor before a moment (default: the outage start) and shortly after: audit-log changes to the monitor and to its escalation policies (regions, URL, timeout, pause / resume..., with | typed |
run_check_now | Run the monitor's check right now from each of its regions (20 at most) and return per region: ok, status, total ms, error, failure layer and phase timings in integer ms (dns, connect, ttfb, download) | typed |
list_healthchecks | Cron/heartbeat healthchecks of the project (jobs that ping Hyperping; monitors are list_monitors, servers list_servers): per healthcheck its hc_ uuid, name, schedule (cron + timezone, or period), grac | typed |
get_healthcheck | One healthcheck in detail: schedule, grace, state and timing, escalation policy, uptime and downtime over the last 30 days, its last 20 pings (pings are kept 15 days; "start" = a /start ping without i | typed |
list_servers | Servers of the project (machines running the Hyperping agent, agt_ uuids; not monitors or healthchecks): per server its name, hostname, status (online, stale = heartbeat late, offline, uninstalled), l | typed |
get_server | One server in detail: status, last seen, OS, agent version (and whether an update exists), hardware, group, tags, escalation policy; current memory and root disk usage; last 24 h of CPU %, memory %, d | typed |
list_audit_log | Who changed what in the project (the Audit Log page; owners and admins, Business plan): newest first, each event with its time, actor (user name and email, or the API key / MCP key that acted, or syst | typed |
get_project_report | Uptime of every monitor of the project over a period, worst first, in one call: per monitor uptime_pct, downtime (seconds + text), outage count, longest outage and MTTR (mean time to resolve, resolved | typed |
get_outage_alerts | Who was notified for one outage, and how: every alert delivery attempt (time, channel email/sms/phonecall/slack/teams/webhook/pagerduty/opsgenie/…, recipient: user name and email, phone as its last 4 | typed |
list_browser_runs | Recent runs of one browser check (Playwright), newest first: when, region, pass or fail, the failing test and the first line of its error, and for checks that retry failures whether the retry passed. | typed |
get_browser_run | One run of a browser check (Playwright) in depth, to explain a failure: each test with its error and failed step, the script's console output, and a digest of the Playwright trace (the actions up to t | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/com-hyperping-hyperping)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.