hyperping

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

CommunityOnlineAPI key requiredGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    An API key from the service settings is required

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

    How to connect

    How to connect hyperping to Claude

    The server address to paste into Claude settings:

    https://api.hyperping.io/v1/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect hyperping to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.hyperping.io/v1/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect hyperping to Cursor

    The server address to paste into Cursor settings:

    https://api.hyperping.io/v1/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (26)

    Raw names from tools/list. Only developers need these.

    list_monitorsPaginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).
    get_monitorFetch a single monitor by its UUID.
    create_monitorCreate a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.
    update_monitorPatch a monitor. Pass only fields you want to change; others are preserved.
    pause_monitorPause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.
    resume_monitorResume a paused monitor. Same as update_monitor with paused=false.
    search_monitors_by_nameCase-insensitive substring search across monitor names and URLs.
    get_status_summaryUp/down/paused counts plus a list of currently down monitors with the timestamp they went down.
    list_outagesPaginated list of outages in the project. Filter by status, type, or search term.
    get_outageFetch a single outage by UUID, including acknowledgements, description, and root cause.
    get_outage_timelineFull activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.
    get_monitor_outagesPaginated list of outages scoped to one monitor. Convenience wrapper around list_outages.
    list_recent_alertsAlert notifications (up/down transitions) over a date range. Defaults to last 30 days.
    get_monitor_uptimeUptime percentage over a date window, aggregated and optionally per day/hour/week/month.
    get_monitor_response_timeResponse 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_mttrMean 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_mttaMean 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_anomaliesAnomaly-detection output for a single monitor (flapping, latency spikes, etc.).
    get_monitor_http_logsRecent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures.
    list_on_call_schedulesAll on-call schedules in the project. Each entry typically includes rotation config and current on-call.
    get_on_call_scheduleOne schedule by UUID with full rotation detail and the linked escalation policies.
    list_escalation_policiesAll escalation policies in the project. Use to find which monitors route alerts where.
    get_escalation_policyOne policy by UUID. Reveals step sequence, linked schedules, and contact channels.
    list_team_membersUsers on the project, with names and emails. Use to resolve user IDs from schedules/policies.
    list_integrationsAll notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).
    get_integrationOne integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.).