Skip to content
External endpointresponds

hyperping

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

Endpoint URL
https://api.hyperping.io/v1/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
246 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.hyperping/hyperping

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
hyperping-monitors
Version
1.0.0
Capability keys
tools
Tool names
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, 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
Instructions excerpt

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. Deletion is intentionally not exposed via MCP — use the dashboard or REST API directly. For observability use get_status_summary (up/down now), list_outages/get_outage/get_monitor_outages (incident

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 375ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 744ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 699ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 246ms
Back to MCP directory