DevOps

hyperping.com

Monitor websites and APIs from multiple locations with frequent checks, plus status pages and on-call scheduling.

1 endpoint26 known toolsFirst detected July 29, 2026Last detected August 29, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: hyperping-monitors
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

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 history), list_recent_alerts (notifications), get_monitor_uptime/response_time/mttr/mtta (reporting), get_monitor_anomalies, get_monitor_http_logs. To answer "who is on-call for monitor X?": get_monitor → get_escalation_policy → get_on_call_schedule → list_team_members. Monitor UUIDs start with "mon_". Project scope and auth are handled automatically from the API key.

Known tools 26

list_monitors

Paginated monitors in the project.

Inferred read-only

get_monitor

Fetch a single monitor by its UUID.

Inferred read-only

create_monitor

Create a new monitor.

Potential side effects

update_monitor

Patch a monitor.

Inferred read-only

pause_monitor

Pause a monitor — no checks run and no alerts fire.

Inferred read-only

resume_monitor

Resume a paused monitor.

Inferred read-only

search_monitors_by_name

Case-insensitive substring search across monitor names and URLs.

Inferred read-only

get_status_summary

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

Inferred read-only

list_outages

Paginated list of outages in the project.

Inferred read-only

get_outage

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

Inferred read-only

get_outage_timeline

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

Inferred read-only

get_monitor_outages

Paginated list of outages scoped to one monitor.

Inferred read-only

list_recent_alerts

Alert notifications (up/down transitions) over a date range.

Inferred read-only

get_monitor_uptime

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

Inferred read-only

get_monitor_response_time

Response time latency trend over a date window.

Inferred read-only

get_monitor_mttr

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

Inferred read-only

get_monitor_mtta

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

Inferred read-only

get_monitor_anomalies

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

Inferred read-only

get_monitor_http_logs

Recent HTTP probe logs for a monitor, paginated.

Inferred read-only

list_on_call_schedules

All on-call schedules in the project.

Inferred read-only

get_on_call_schedule

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

Inferred read-only

list_escalation_policies

All escalation policies in the project.

Inferred read-only

get_escalation_policy

One policy by UUID.

Inferred read-only

list_team_members

Users on the project, with names and emails.

Inferred read-only

list_integrations

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

Potential side effects

get_integration

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.hyperping-monitors]
url = "https://api.hyperping.io/v1/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: hyperping-monitors
Remote MCP URL: https://api.hyperping.io/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "hyperping-monitors": {
      "url": "https://api.hyperping.io/v1/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "hyperping-monitors": {
      "type": "http",
      "url": "https://api.hyperping.io/v1/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "hyperping-monitors",
  "transport": "streamable-http",
  "url": "https://api.hyperping.io/v1/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for hyperping.io was fetched 2026-08-29T10:49:08.080Z.

Trust status Trusted

hyperping.io is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.