mcp server
hyperping
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Description as published by the maintainer. Source
- version 1.0.0
- active
- analytics
active — Most recent push to the repository was 2026-07-30. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
26 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
create_monitor(url, name, port, paused, regions, timeout, group_id, protocol, alerts_wait, http_method, request_body, dns_nameserver, check_frequency, dns_record_type, request_headers, follow_redirects, required_keyword, escalation_policy, dns_expected_answer, expected_status_code)- Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks. Required: name, url.
get_escalation_policy(uuid)- One policy by UUID. Reveals step sequence, linked schedules, and contact channels. Required: uuid.
get_integration(uuid)- One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.). Required: uuid.
get_monitor(uuid)- Fetch a single monitor by its UUID. Required: uuid.
get_monitor_anomalies(uuid)- Anomaly-detection output for a single monitor (flapping, latency spikes, etc.). Required: uuid.
get_monitor_http_logs(page, uuid, level, limit)- Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures. Required: uuid.
get_monitor_mtta(to, from, monitor_uuids)- Mean time to acknowledge (MTTA) per monitor over a date window, in seconds.
get_monitor_mttr(to, from, monitor_uuids)- Mean time to resolve (MTTR) per monitor over a date window, in seconds.
get_monitor_outages(page, status, monitor_uuid)- Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages. Required: monitor_uuid.
get_monitor_response_time(to, from, resolution, monitor_uuids)- Response time latency trend over a date window.
get_monitor_uptime(to, from, resolution, monitor_uuids)- Uptime percentage over a date window, aggregated and optionally per day/hour/week/month.
get_on_call_schedule(uuid)- One schedule by UUID with full rotation detail and the linked escalation policies. Required: uuid.
get_outage(uuid)- Fetch a single outage by UUID, including acknowledgements, description, and root cause. Required: uuid.
get_outage_timeline(uuid)- Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution. Required: 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(page, limit, status)- Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).
list_on_call_schedules- All on-call schedules in the project. Each entry typically includes rotation config and current on-call.
list_outages(page, type, search, status)- Paginated list of outages in the project. Filter by status, type, or search term.
list_recent_alerts(to, from, resolution, monitor_uuids)- Alert notifications (up/down transitions) over a date range. Defaults to last 30 days.
list_team_members- Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.
pause_monitor(uuid)- Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true. Required: uuid.
resume_monitor(uuid)- Resume a paused monitor. Same as update_monitor with paused=false. Required: uuid.
search_monitors_by_name(query)- Case-insensitive substring search across monitor names and URLs. Required: query.
update_monitor(url, name, port, uuid, paused, regions, timeout, group_id, protocol, alerts_wait, http_method, request_body, dns_nameserver, check_frequency, dns_record_type, request_headers, follow_redirects, required_keyword, escalation_policy, dns_expected_answer, expected_status_code)- Patch a monitor. Pass only fields you want to change; others are preserved. Required: uuid.
Last successful function declaration observed on . Source: https://api.hyperping.io/v1/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.hyperping.io/v1/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-30 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-29 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-29 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 26 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.hyperping.io | |
| mcp endpoint status | ok | The server listed 26 functions when asked. | as of probe | api.hyperping.io |
Where to get it
Related, by what their authors tagged them
-
DebugBundle
— last commit 2026-07-29, shares incident-management, observability
DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.
-
FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe
— last commit 2026-08-06, shares observability, on-call
FastMCP server that pages on-call via 100+ notification channels (Apprise wrapper)
-
io.github.cyanheads/devops-status-mcp-server
— last commit 2026-07-31, shares monitoring, sre
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
-
io.github.Areso/safe-ssh-mcp
— last commit 2026-06-04, shares observability, sre
A secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands
-
Servonaut
— last commit 2026-08-05, shares sre
Manage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec.
-
io.github.arnavranjan005/mcp-telemetry-server
— last commit 2026-07-29, shares monitoring, observability
Streams live progress from mcp-telemetry-sdk-instrumented tools to any connected MCP client.
-
io.github.dynatrace-oss/Dynatrace-mcp
— last commit 2026-07-24, shares monitoring, observability
[DEPRECATED] Dynatrace MCP Server. Migrate to dynatrace-for-ai or Dynatrace Remote MCP Server.
-
io.github.fishcoco-code/guardrly-mcp
— last commit 2026-04-17, shares monitoring, observability
Non-invasive AI Agent monitoring — audit every API call to Shopify, Meta Ads, and more
-
World Monitor
— last commit 2026-08-06, shares monitoring
Live global intelligence: real-time markets, conflicts, country risk, chokepoints, energy. 39 tools.
-
com.clauxel.agentmonitorrelay/agentmonitorrelay-mcp
— last commit 2026-05-19, shares monitoring
AI agent run monitoring with incident replay and SLA receipts.
These share tags the maintainers applied themselves, such as incident-management, observability, on-call, monitoring. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: incident-management, mcp, mcp-server, model-context-protocol, monitoring, observability, on-call, sre, status-page, uptime-monitoring.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json