Hyperping

Connect Remote server

claude mcp add --transport http hyperping https://api.hyperping.io/v1/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

{
  "mcpServers": {
    "hyperping": {
      "url": "https://api.hyperping.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "hyperping": {
      "type": "http",
      "url": "https://api.hyperping.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Settings > Connectors > Add custom connector
URL: https://api.hyperping.io/v1/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 69 found in our last check

• list_monitors

  Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).

• get_monitor

  Fetch a single monitor by its UUID.

• create_monitor

  Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.

• update_monitor

  Patch a monitor. Pass only fields you want to change; others are preserved.

• pause_monitor

  Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.

• resume_monitor

  Resume a paused monitor. Same as update_monitor with paused=false.

• search_monitors_by_name

  Case-insensitive substring search across monitor names and URLs.

• get_status_summary

  Up/down/paused counts plus a list of currently down monitors with the timestamp they went down.

• list_outages

  Paginated list of outages in the project. Filter by status, type, or search term.

• get_outage

  Fetch a single outage by UUID, including acknowledgements, description, and root cause.

• get_outage_timeline

  Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.

• get_monitor_outages

  Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages.

• 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 published on a status page (create_status_page_incident does that).

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

• escalate_outage

  Page the next step of the outage's escalation policy now instead of waiting for it. Each call moves one step further.

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

• list_recent_alerts

  Alert notifications (up/down transitions) over a date range. Defaults to last 30 days.

• get_monitor_uptime

  Uptime percentage over a date window, aggregated and optionally per day/hour/week/month.

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

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

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

• get_monitor_anomalies

  Anomaly-detection output for a single monitor (flapping, latency spikes, etc.).

• get_monitor_http_logs

  Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures.

• list_on_call_schedules

  All on-call schedules in the project. Each entry typically includes rotation config and current on-call.

• get_on_call_schedule

  One schedule by UUID with full rotation detail and the linked escalation policies.

• list_escalation_policies

  All escalation policies in the project. Use to find which monitors route alerts where.

• get_escalation_policy

  One policy by UUID. Reveals step sequence, linked schedules, and contact channels.

• list_team_members

  Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.

• 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 the escalation policies each schedule pages for. Use it for any "who is on call…

• list_integrations

  All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).

• get_integration

  One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.).

• list_status_pages

  Status pages in the project, 20 per page: UUID, name, public URL, password protection.

• 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).

• 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 user first. Password protection, SSO, a custom domain and a logo are set in the…

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

• 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 where they are. A healthcheck shows its uptime bar (show_uptime) but never resp…

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

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

• get_status_page_incident

  One status page incident with every update (newest first, with their UUIDs), its status pages and affected components.

• 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 internally and page on-call instead, use create_outage.

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

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

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

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

• list_maintenance_windows

  Maintenance windows, 20 per page, with their monitors, status pages, updates and status (upcoming, inprogress, completed).

• get_maintenance_window

  One maintenance window with its updates and the state of its subscriber notification.

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

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

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

• 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_maintenance_window.

• 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:error or level:>=warn, attr.<key>:value, trace:<id>, pattern:<hash>, word* for a…

• 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-level histogram. Works for monitor, manual, server, log-rule and healthcheck (hco…

• 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), level, services, hosts, first/last seen, one sample. Computed from the store…

• 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 one with run_log_chart; dashboard variables such as $service must be passed in `v…

• 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> | <aggregations> [by <fields>] [every <interval>] [compare <1h|1d|1w|4w>] [| eval <alia…

• 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's fields (HTTP status, duration, route…) are detected in the project's logs; p…

• 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_region" or "unknown" —, the dominant failure layer (dns, connect, tls, timeout, ht…

• 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 ongoing, status code, error, host, registrable domain, resolved IP and detectin…

• 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 who made them; needs the owner or admin role and the plan that includes the Au…

• 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), once every region answered or after about 25 s (regions still waiting are lis…

• 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), grace period, state (down, up, or new = never pinged), paused: true when paused (no…

• 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 its completion, "fail" = a run the job reported failed) and its last 10 incident…

• 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), last_seen_at, OS, agent version, group, tags, current memory_pct and disk_pct of…

• 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 %, disk % (all filesystems) and 1-minute load as last/avg/max of 5-minute averages;…

• 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 system), action (e.g. UpdateMonitor, DeleteStatuspage, InviteUser, MuteOutage), res…

• 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 outages only), plus project totals (average uptime, total downtime and outages…

• 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 digits, or the integration name; down or up; escalation step) with its status:…

• 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. Failed runs only by default, over the last 7 days. Then read one with get_brows…

• 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 the failure with their call log and script line, failed network requests, browse…

Headers

Details

More cloud and devops servers See all

• OxyPages

  Deploy HTML pages and built web apps (React, Vue, Vite) to a live HTTPS link from your AI agent.

• Privi Call

  One number per AI agent: route MCP calls to any agent, every call sealed in an on-chain log.

• OldWeb Diagnostics

  Public DNS, HTTPS and deployment checks, plus offline email header and delivery-log tracing.

• OldWeb Logs

  Offline log parsing, CI failures, HTTP capture analysis and bounded JSON configuration validation.

• TrainRec

  Your AI assistant logs your meals and workouts, then plans your week from what you did.

• ZeroPhase

  BUD/S prep training: read today's workout, log tasks and PST results from your agent.