Connect Hyperping and your agent gets 26 tools, among them create_monitor, get_escalation_policy, get_integration. It answers at https://api.hyperping.io/v1/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_monitor | Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks. Inputs: name, url, protocol, port, http_method, regions |
get_escalation_policy | One policy by UUID. Reveals step sequence, linked schedules, and contact channels. Inputs: uuid |
get_integration | One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.). Inputs: uuid |
get_monitor | Fetch a single monitor by its UUID. Inputs: uuid |
get_monitor_anomalies | Anomaly-detection output for a single monitor (flapping, latency spikes, etc.). Inputs: uuid |
get_monitor_http_logs | Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures. Inputs: uuid, page, limit, level |
get_monitor_mtta | Mean time to acknowledge (MTTA) per monitor over a date window, in seconds. Inputs: from, to, monitor_uuids |
get_monitor_mttr | Mean time to resolve (MTTR) per monitor over a date window, in seconds. Inputs: from, to, monitor_uuids |
get_monitor_outages | Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages. Inputs: monitor_uuid, page, status |
get_monitor_response_time | Response time latency trend over a date window. Inputs: from, to, monitor_uuids, resolution |
get_monitor_uptime | Uptime percentage over a date window, aggregated and optionally per day/hour/week/month. Inputs: from, to, monitor_uuids, resolution |
get_on_call_schedule | One schedule by UUID with full rotation detail and the linked escalation policies. Inputs: uuid |
get_outage | Fetch a single outage by UUID, including acknowledgements, description, and root cause. Inputs: uuid |
get_outage_timeline | Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution. Inputs: uuid |
get_status_summary | Up/down/paused counts plus a list of currently down monitors with the timestamp they went down. |
list_escalation_policies | All escalation policies in the project. Use to find which monitors route alerts where. |
list_integrations | All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.). |
list_monitors | Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring). Inputs: status, page, limit |
list_on_call_schedules | All on-call schedules in the project. Each entry typically includes rotation config and current on-call. |
list_outages | Paginated list of outages in the project. Filter by status, type, or search term. Inputs: page, search, status, type |
list_recent_alerts | Alert notifications (up/down transitions) over a date range. Defaults to last 30 days. Inputs: from, to, resolution, monitor_uuids |
list_team_members | Users on the project, with names and emails. Use to resolve user IDs from schedules/policies. |
pause_monitor | Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true. Inputs: uuid |
resume_monitor | Resume a paused monitor. Same as update_monitor with paused=false. Inputs: uuid |
search_monitors_by_name | Case-insensitive substring search across monitor names and URLs. Inputs: query |
update_monitor | Patch a monitor. Pass only fields you want to change; others are preserved. Inputs: uuid, name, url, protocol, port, http_method |
Every block below points at https://api.hyperping.io/v1/mcp. Pick your client and copy.
claude mcp add --transport http hyperping https://api.hyperping.io/v1/mcp
{
"mcpServers": {
"hyperping": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.hyperping.io/v1/mcp"]
}
}
}{
"mcpServers": {
"hyperping": {
"url": "https://api.hyperping.io/v1/mcp"
}
}
}{
"servers": {
"hyperping": {
"type": "http",
"url": "https://api.hyperping.io/v1/mcp"
}
}
}{
"context_servers": {
"hyperping": {
"url": "https://api.hyperping.io/v1/mcp"
}
}
}{
"mcpServers": {
"hyperping": {
"serverUrl": "https://api.hyperping.io/v1/mcp"
}
}
}{
"mcpServers": {
"hyperping": {
"url": "https://api.hyperping.io/v1/mcp"
}
}
}name: hyperping
version: 0.0.1
schema: v1
mcpServers:
- name: hyperping
type: streamable-http
url: https://api.hyperping.io/v1/mcp{
"mcpServers": {
"hyperping": {
"httpUrl": "https://api.hyperping.io/v1/mcp"
}
}
}{
"mcpServers": {
"hyperping": {
"type": "http",
"url": "https://api.hyperping.io/v1/mcp"
}
}
}{
"mcpServers": {
"hyperping": {
"url": "https://api.hyperping.io/v1/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.hyperping.io%2Fv1%2Fmcp&type=streamable_http&id=hyperping&name=hyperping
It answered our last check on 18 October 2026 in 132 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
26, as returned by the server's own tools/list on 31 August 2026: create_monitor, get_escalation_policy, get_integration, get_monitor, get_monitor_anomalies, get_monitor_http_logs, get_monitor_mtta, get_monitor_mttr, and 18 more.
It answered our last check on 18 October 2026 in 132 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.hyperping.io/v1/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.hyperping. Endpoint host: api.hyperping.io. ARD identifier: urn:air:com.hyperping:mcp:hyperping.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.