← MCP Reliability Index / Web & Scraping

Hyperping

com.hyperping/hyperping

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

healthy

status

tools exposed

1950ms

connect latency

c38bef58947c

schema fingerprint

Tools (26)

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.

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.

get_monitor_mttr

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

get_monitor_mtta

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

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.

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

Endpoint

https://api.hyperping.io/v1/mcp
Category: Web & Scraping · Last checked: 2026-08-15T09:06:34Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access

How we measure →

What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.