mocop
Browse · Docs · Guide · Analyze

hyperping-monitors

MCP server by Hyperping · mcp

Hyperping synthetic-monitoring tools, scoped to the authenticated project. RATE LIMITS per project. Per minute: initialize=5, tools/list=30, tools/call=60. Per hour: initialize=20, tools/list=200, tools/call=600. BOTH windows apply — slowing down within a minute is not enough if you exceed the hourly cap. Exceeding any of these returns a JSON-RPC error with a Retry-After hint. To stay under the limit: open the MCP session ONCE at startup and reuse it for every tool call — do NOT call "initialize" again per request. Batch related questions into fewer tool calls when possible. If you receive a rate_limit_exceeded error, wait the indicated retry_after_seconds before retrying. Monitors are the center of gravity. Manage them with list/get/create/update/pause/resume/search_monitors_by_name. For observability use get_status_summary (up/down now), list_recent_alerts (notifications), get_monitor_uptime/response_time/mttr/mtta (reporting), get_monitor_anomalies, get_monitor_http_logs. Incident…

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

Verification: observed. Source: crawl.

Capabilities (69)

  • 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
About · Contact · Privacy