com.hyperping/hyperping

up checked 2026-11-10T22:37:33.870Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided description

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

Summary by lookupd

Lets an agent manage uptime monitors, check outage and on-call status, acknowledge or escalate incidents, and review uptime and…

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http hyperping https://api.hyperping.io/v1/mcp

Codex, remote (streamable-http)

codex mcp add hyperping --url https://api.hyperping.io/v1/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "hyperping": {
      "url": "https://api.hyperping.io/v1/mcp"
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (showing 30 of 69)

Publisher-provided text

• 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 o
• 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
• 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 m
• 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 thi
• 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
• 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, emai
• list_integrations All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).

Details

• Version: 1.0.0
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 674 ms
• First indexed: 2026-11-01T08:54:33.231Z
• Last seen in registry: 2026-11-01T08:54:33.231Z
• Repository: https://github.com/hyperping/mcp-server
• Website: https://hyperping.com/docs/mcp

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/com.hyperping/hyperping.svg)](https://lookupd.com/servers/com.hyperping/hyperping)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp