# com.hyperping/hyperping (remote · api.hyperping.io)

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

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.hyperping.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-hyperping-hyperping/v1-mcp.md), [page](https://verifymcp.io/servers/com-hyperping-hyperping/v1-mcp)

## Channel facts

- Endpoint: `https://api.hyperping.io/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2368 tokens (~91/item across 26 items; 26 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.com-hyperping-hyperping]
url = "https://api.hyperping.io/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hyperping-hyperping": {
      "type": "remote",
      "url": "https://api.hyperping.io/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hyperping-hyperping --url https://api.hyperping.io/v1/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hyperping-hyperping:
    url: "https://api.hyperping.io/v1/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-hyperping-hyperping": {
      "type": "http",
      "url": "https://api.hyperping.io/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 74, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 70, +49)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 21)

First indexed and scored.

## MCP tools (26)

### `list_monitors` (~85 tokens)

List monitors

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

Input parameters:

- `limit` (integer): Rows per page. Default 50, max 200.
- `page` (integer): Zero-indexed page. Default 0.
- `status` (string): Filter by state. "ssl_expiring" = SSL expires within 30 days.

### `get_monitor` (~30 tokens)

Get monitor

Fetch a single monitor by its UUID.

Input parameters:

- `uuid` (string, required): Monitor UUID (format "mon_...")

### `create_monitor` (~369 tokens)

Create monitor

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

Input parameters:

- `alerts_wait` (number): Minutes to wait before alerting. -1 disables, 0 is immediate.
- `check_frequency` (number): Check interval in seconds. Sub-30s requires a business plan.
- `dns_expected_answer` (string): Expected DNS answer to assert against.
- `dns_nameserver` (string): Custom nameserver for DNS checks.
- `dns_record_type` (string): DNS record type (protocol="dns").
- `escalation_policy` (string): UUID of an escalation policy to link.
- `expected_status_code` (string|number): Expected response status: number (200), "2xx", or "1xx-3xx".
- `follow_redirects` (boolean): Follow 3xx redirects on http monitors.
- `group_id`: Group to place the monitor in.
- `http_method` (string): HTTP verb. Defaults to GET.
- `name` (string, required): Human-readable monitor name.
- `paused` (boolean): Start the monitor in a paused state.
- `port` (integer): TCP port — required when protocol is "port".
- `protocol` (string): Check protocol. Defaults to "http".
- `regions` (array): Probe region codes, e.g. ["us-east","eu-west"]. Use ["*"] for all.
- `request_body` (string): Body for http requests.
- `request_headers` (array): Custom request headers.
- `required_keyword` (string): Body must contain this keyword, else flagged down.
- `timeout` (integer): Request timeout in seconds (default 30).
- `url` (string, required): Target URL (http) or hostname (icmp/port/dns).

### `update_monitor` (~372 tokens)

Update monitor

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

Input parameters:

- `alerts_wait` (number): Minutes to wait before alerting. -1 disables, 0 is immediate.
- `check_frequency` (number): Check interval in seconds. Sub-30s requires a business plan.
- `dns_expected_answer` (string): Expected DNS answer to assert against.
- `dns_nameserver` (string): Custom nameserver for DNS checks.
- `dns_record_type` (string): DNS record type (protocol="dns").
- `escalation_policy` (string): UUID of an escalation policy to link.
- `expected_status_code` (string|number): Expected response status: number (200), "2xx", or "1xx-3xx".
- `follow_redirects` (boolean): Follow 3xx redirects on http monitors.
- `group_id`: Group to place the monitor in.
- `http_method` (string): HTTP verb. Defaults to GET.
- `name` (string): Human-readable monitor name.
- `paused` (boolean): Start the monitor in a paused state.
- `port` (integer): TCP port — required when protocol is "port".
- `protocol` (string): Check protocol. Defaults to "http".
- `regions` (array): Probe region codes, e.g. ["us-east","eu-west"]. Use ["*"] for all.
- `request_body` (string): Body for http requests.
- `request_headers` (array): Custom request headers.
- `required_keyword` (string): Body must contain this keyword, else flagged down.
- `timeout` (integer): Request timeout in seconds (default 30).
- `url` (string): Target URL (http) or hostname (icmp/port/dns).
- `uuid` (string, required): UUID of the monitor to update.

### `pause_monitor` (~41 tokens)

Pause monitor

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

Input parameters:

- `uuid` (string, required): UUID of the monitor to pause.

### `resume_monitor` (~34 tokens)

Resume monitor

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

Input parameters:

- `uuid` (string, required): UUID of the monitor to resume.

### `search_monitors_by_name` (~39 tokens)

Search monitors by name

Case-insensitive substring search across monitor names and URLs.

Input parameters:

- `query` (string, required): Case-insensitive substring matched against monitor names or URLs.

### `get_status_summary` (~28 tokens)

Status summary

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

### `list_outages` (~97 tokens)

List outages

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

Input parameters:

- `page` (integer): Zero-indexed page number, 20 outages per page.
- `search` (string): Substring matched against monitor name/URL/domain or "INC-123".
- `status` (string): Filter by status. Defaults to "all".
- `type` (string): Filter by type. Defaults to "all".

### `get_outage` (~36 tokens)

Get outage

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

Input parameters:

- `uuid` (string, required): Outage UUID.

### `get_outage_timeline` (~54 tokens)

Get outage timeline

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

Input parameters:

- `uuid` (string, required): Outage UUID (format "outage_..." or "INC-123").

### `get_monitor_outages` (~79 tokens)

Get outages for a monitor

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

Input parameters:

- `monitor_uuid` (string, required): Monitor UUID (format "mon_...") to filter by.
- `page` (integer): Zero-indexed page number, 20 per page.
- `status` (string): Filter by status. Defaults to "all".

### `list_recent_alerts` (~90 tokens)

List recent alerts

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

Input parameters:

- `from` (string): ISO start date. Default: 30 days ago.
- `monitor_uuids` (array): Restrict to these monitor UUIDs.
- `resolution` (string): Time grouping. Default "day".
- `to` (string): ISO end date. Default: now.

### `get_monitor_uptime` (~88 tokens)

Get uptime (SLA) stats

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

Input parameters:

- `from` (string): ISO start date. Default: 30 days ago.
- `monitor_uuids` (array): Restrict to these monitor UUIDs.
- `resolution` (string): Time grouping. Default "day".
- `to` (string): ISO end date. Default: now.

### `get_monitor_response_time` (~80 tokens)

Get response time

Response time latency trend over a date window.

Input parameters:

- `from` (string): ISO start date. Default: 30 days ago.
- `monitor_uuids` (array): Restrict to these monitor UUIDs.
- `resolution` (string): Time grouping. Default "day".
- `to` (string): ISO end date. Default: now.

### `get_monitor_mttr` (~76 tokens)

Get MTTR per monitor

Mean time to resolve (MTTR) per monitor over a date window, in seconds.

Input parameters:

- `from` (string): ISO start date. Default: 30 days ago.
- `monitor_uuids` (array): Restrict to these monitor UUIDs.
- `to` (string): ISO end date. Default: now.

### `get_monitor_mtta` (~76 tokens)

Get MTTA per monitor

Mean time to acknowledge (MTTA) per monitor over a date window, in seconds.

Input parameters:

- `from` (string): ISO start date. Default: 30 days ago.
- `monitor_uuids` (array): Restrict to these monitor UUIDs.
- `to` (string): ISO end date. Default: now.

### `get_monitor_anomalies` (~44 tokens)

Get monitor anomalies

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

Input parameters:

- `uuid` (string, required): Monitor UUID (format "mon_...").

### `get_monitor_http_logs` (~87 tokens)

Get monitor HTTP logs

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

Input parameters:

- `level` (array): Filter by log level.
- `limit` (integer): Rows per page. Default 50, max 200.
- `page` (integer): Zero-indexed page. Default 0.
- `uuid` (string, required): Monitor UUID (format "mon_...").

### `list_on_call_schedules` (~30 tokens)

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` (~39 tokens)

Get on-call schedule

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

Input parameters:

- `uuid` (string, required): Schedule UUID (format "sch_...").

### `list_escalation_policies` (~28 tokens)

List escalation policies

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

### `get_escalation_policy` (~46 tokens)

Get escalation policy

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

Input parameters:

- `uuid` (string, required): Escalation policy UUID (format "esc_...").

### `list_team_members` (~29 tokens)

List team members

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

### `list_integrations` (~35 tokens)

List integrations

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

### `get_integration` (~45 tokens)

Get integration

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

Input parameters:

- `uuid` (string, required): Integration UUID (format "int_...").

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hyperping-hyperping/v1-mcp#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 75
- 2026-08-01: 74
- 2026-07-31: 70
- 2026-07-30: 21
- 2026-07-29: 21

## Links

- Remote endpoint: https://api.hyperping.io/v1/mcp
- Authorisation metadata: https://api.hyperping.io/.well-known/oauth-protected-resource/v1/mcp
- Repository: https://github.com/hyperping/mcp-server
- Website: https://hyperping.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-hyperping-hyperping/v1-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hyperping-hyperping/v1-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-hyperping-hyperping/v1-mcp