Hyperping MCP Server

MCP serverMonitoring & ops

hyperping keeps watch over your websites, APIs, and servers and tells you when something goes down. Once it is added, your AI can check the current status of your services, review past outages, and help you manage who gets alerted when problems happen.

Use Hyperping MCP Server in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Hyperping MCP Server and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use Hyperping MCP Server to list monitors

Details

Available today. Use it from your connected AI after setup.

Add hyperping, then ask your AI to check the current status of your services or walk you through setting up monitoring for a new site.

Hyperping MCP ServerStart free

What your AI can do with it

  • Check whether your websites, APIs, and servers are up right now
  • Review past outages and monitoring reports
  • Manage on-call schedules so the right person gets alerted
  • Update your public status pages

Install Hyperping MCP Server

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user hyperping-mcp-server 'https://api.hyperping.io/v1/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

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

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=hyperping-mcp-server&config=eyJ1cmwiOiJodHRwczovL2FwaS5oeXBlcnBpbmcuaW8vdjEvbWNwIn0=

    Open the link and Cursor adds the server at that address.

  • ChatGPT

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

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

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

    Run it once, then sign in with codex mcp login hyperping-mcp-server if the server asks for an account.

From the project's README

As published by hyperping/mcp-server in README.md.

Official Model Context Protocol server for Hyperping. It exposes uptime monitoring, incident history, on-call schedules and reporting to AI agents over HTTP.

This is a remote server. There is nothing to install or self-host: point your client at the endpoint with an API key. This repository holds the registry manifest, the client configuration and the tool reference.

Full documentation: hyperping.com/docs/mcp

Endpoint

URLhttps://api.hyperping.io/v1/mcp
TransportStreamable HTTP, JSON-RPC 2.0
AuthBearer token
ScopeOne project per key
Tools26 (22 read, 4 write)

Quick start

  1. In Hyperping, go to Project Settings, API Keys and create a read_only or read_write key.
  2. Add the server to your MCP client (see below).
  3. Restart the client, then ask it things like "what is down right now?" or "what was our uptime on the API monitor last month?"

Claude Desktop, Claude Code, Cursor, Windsurf

{
  "mcpServers": {
    "hyperping": {
      "type": "http",
      "url": "https://api.hyperping.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer sk_..."
      }
    }
  }
}

stdio clients

Clients that only speak stdio can bridge through mcp-remote:

{
  "mcpServers": {
    "hyperping": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.hyperping.io/v1/mcp",
        "--header",
        "Authorization: Bearer sk_..."
      ]
    }
  }
}

Tools

Monitors

ToolScopeDescription
list_monitorsreadPaginated monitors, filterable by up, down, paused, ssl_expiring.
get_monitorreadOne monitor by UUID.
search_monitors_by_namereadCase-insensitive substring search over names and URLs.
create_monitorwriteCreate an HTTP, ICMP, port or DNS monitor.
update_monitorwritePatch a monitor. Unspecified fields are preserved.
pause_monitorwriteStop checks and alerts for a monitor.
resume_monitorwriteResume a paused monitor.

delete_monitor is deliberately not exposed. Use the dashboard or the REST API.

Status and outages

ToolScopeDescription
get_status_summaryreadUp, down and paused counts, plus what is currently down and since when.
list_outagesreadPaginated outages, filterable by status, type or search term.
get_outagereadOne outage, with acknowledgements, description and root cause.
get_outage_timelinereadDetection, cross-region verification, alert dispatch, acknowledgement, resolution.
get_monitor_outagesreadOutages scoped to a single monitor.

Reporting

ToolScopeDescription
get_monitor_uptimereadUptime percentage over a window, by hour, day, week or month.
get_monitor_response_timereadLatency trend over a window.
get_monitor_mttrreadMean time to resolve, in seconds.
get_monitor_mttareadMean time to acknowledge, in seconds.

Diagnostics

ToolScopeDescription
get_monitor_anomaliesreadFlapping, latency spikes and other detected anomalies.
get_monitor_http_logsreadRecent HTTP probe logs, filterable by level.
list_recent_alertsreadUp and down notifications over a date range.

On-call

ToolScopeDescription
list_on_call_schedulesreadAll schedules, with rotation config and current on-call.
get_on_call_schedulereadOne schedule, with full rotation detail and linked policies.
list_escalation_policiesreadAll escalation policies in the project.
get_escalation_policyreadOne policy, with step sequence, schedules and contact channels.
list_team_membersreadProject users, to resolve IDs coming from schedules and policies.

To answer "who is on call for monitor X?", chain get_monitor, get_escalation_policy, get_on_call_schedule, list_team_members.

Integrations

ToolScopeDescription
list_integrationsreadSlack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook and others.
get_integrationreadOne integration, with its channel-specific config.

Rate limits

Limits apply per project, and both windows are enforced.

MethodPer minutePer hour
initialize520
tools/list30200
tools/call60600

Open the session once and reuse it rather than calling initialize per request. Exceeding a limit returns a JSON-RPC error with a retry_after_seconds hint.

Machine-readable spec

For a dense, agent-friendly spec covering tools, query patterns and response shapes, point your client at hyperping.com/mcp/llms.txt.

Support

Open an issue here, or reach the team through hyperping.com/contact/sales.

License

MIT for the contents of this repository. Use of the hosted service is governed by the Hyperping terms and privacy policy.

Tools it offers (49)

What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.

  • list_monitors
  • get_monitor
  • create_monitor
  • update_monitor
  • pause_monitor
  • resume_monitor
  • search_monitors_by_name
  • get_status_summary
  • list_outages
  • get_outage
  • get_outage_timeline
  • get_monitor_outages
  • create_outage
  • acknowledge_outage
  • escalate_outage
  • resolve_outage
  • list_recent_alerts
  • get_monitor_uptime
  • get_monitor_response_time
  • get_monitor_mttr
  • get_monitor_mtta
  • get_monitor_anomalies
  • get_monitor_http_logs
  • list_on_call_schedules
  • get_on_call_schedule
  • list_escalation_policies
  • get_escalation_policy
  • list_team_members
  • list_integrations
  • get_integration

Signals

GitHub stars
1
Last commit
Jul 2026
Advanced
Delivery
hyperping MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
com-hyperping-hyperping
Source
github.com/hyperping/mcp-server
Hosted endpoint
https://api.hyperping.io/v1/mcp