hyperping by hyperping.com
MCP server · Observability & incidents · indexed, not reviewed
Hostedvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Facts
- MCP registry
com.hyperping/hyperping· 1.0.0- Endpoint
https://api.hyperping.io/v1/mcp- Website
- hyperping.com/docs/mcp
- GitHub stars
- 1
- Registry entry
- updated 29 Jul 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under hyperping.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 67 · about 18,757 tokens of context · checked 20 hours ago
| Tool | What it does | Hint |
|---|---|---|
list_monitorsList monitors | Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring). | read-only |
get_monitorGet monitor | Fetch a single monitor by its UUID. | read-only |
create_monitorCreate monitor | Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks. | writes |
update_monitorUpdate monitor | Patch a monitor. Pass only fields you want to change; others are preserved. | writes |
pause_monitorPause monitor | Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true. | writes |
resume_monitorResume monitor | Resume a paused monitor. Same as update_monitor with paused=false. | writes |
search_monitors_by_nameSearch monitors by name | Case-insensitive substring search across monitor names and URLs. | read-only |
get_status_summaryStatus summary | Up/down/paused counts plus a list of currently down monitors with the timestamp they went down. | read-only |
list_outagesList outages | Paginated list of outages in the project. Filter by status, type, or search term. | read-only |
get_outageGet outage | Fetch a single outage by UUID, including acknowledgements, description, and root cause. | read-only |
get_outage_timelineGet outage timeline | Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution. | read-only |
get_monitor_outagesGet outages for a monitor | Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages. | read-only |
create_outageDeclare an incident | Declare an incident by hand, for a problem no monitor detects. It appears under Incident Management in the dashboard and, with an escalation policy, pages its on-call responders. Internal: nothing is published on a… | writes |
acknowledge_outageAcknowledge outage | Mark an ongoing outage as being handled: repeat alerts stop. Escalation steps still fire on schedule; resolve it or fix the cause to stop them. | writes |
escalate_outageEscalate outage | Page the next step of the outage's escalation policy now instead of waiting for it. Each call moves one step further. | writes |
resolve_outageResolve outage | Resolve an incident declared by hand or a server incident, and send the recovery to the channels it paged. An outage detected on a monitor resolves itself when its checks pass again. | writes |
list_recent_alertsList recent alerts | Alert notifications (up/down transitions) over a date range. Defaults to last 30 days. | read-only |
get_monitor_uptimeGet uptime (SLA) stats | Uptime percentage over a date window, aggregated and optionally per day/hour/week/month. | read-only |
get_monitor_response_timeGet response time | Response time latency trend over a date window. Returns a per-monitor breakdown — pass all monitors at once in monitor_uuids rather than calling this once per monitor. | read-only |
get_monitor_mttrGet MTTR per monitor | Mean time to resolve (MTTR) per monitor over a date window, in seconds. Already per-monitor — pass all monitors at once in monitor_uuids rather than calling this once per monitor. | read-only |
get_monitor_mttaGet MTTA per monitor | Mean time to acknowledge (MTTA) per monitor over a date window, in seconds. Already per-monitor — pass all monitors at once in monitor_uuids rather than calling this once per monitor. | read-only |
get_monitor_anomaliesGet monitor anomalies | Anomaly-detection output for a single monitor (flapping, latency spikes, etc.). | read-only |
get_monitor_http_logsGet monitor HTTP logs | Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures. | read-only |
list_on_call_schedulesList on-call schedules | All on-call schedules in the project. Each entry typically includes rotation config and current on-call. | read-only |
get_on_call_scheduleGet on-call schedule | One schedule by UUID with full rotation detail and the linked escalation policies. | read-only |
list_escalation_policiesList escalation policies | All escalation policies in the project. Use to find which monitors route alerts where. | read-only |
get_escalation_policyGet escalation policy | One policy by UUID. Reveals step sequence, linked schedules, and contact channels. | read-only |
list_team_membersList team members | Users on the project, with names and emails. Use to resolve user IDs from schedules/policies. | read-only |
get_on_call_nowWho is on call | Who is on call, per on-call schedule, right now or at the moment given in `at` (e.g. next Saturday 10:00), computed by the engine that pages people: names, emails and the rotation of each person, and the escalation… | read-only |
list_integrationsList integrations | All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.). | read-only |
get_integrationGet integration | One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.). | read-only |
list_status_pagesList status pages | Status pages in the project, 20 per page: UUID, name, public URL, password protection. | read-only |
get_status_pageGet status page | One status page with its settings (languages, subscriptions, access) and the services it shows, section by section, with their UUIDs. | read-only |
create_status_pageCreate status page | Create a status page on a hyperping.app subdomain, with sections of monitors, components and servers. It is public as soon as it exists: confirm the name, address and services with the user first. Password protection,… | writes |
update_status_pageUpdate status page settings | Change a status page's name, description, website, look or subscription button. Only the fields passed change. The page is public: confirm the change with the user first. | writes |
add_status_page_servicesAdd services to status page | Show monitors, components or servers on a status page, in the section you name (created at the end if the page has none by that name) or the first one. Services already on the page stay where they are. | writes |
remove_status_page_servicesRemove services from status page | Take monitors, components or servers off a status page, wherever they appear, groups included. Their settings on the page (display name, description) are lost. | writes |
list_status_page_incidentsList status page incidents | Incidents published on status pages, newest first, each with its current stage and latest update. For downtime detected on monitors, use list_outages. | read-only |
get_status_page_incidentGet status page incident | One status page incident with every update (newest first, with their UUIDs), its status pages and affected components. | read-only |
create_status_page_incidentPublish status page incident | Publish an incident on status pages, with its first update. Public, and emailed to subscribers unless notify_subscribers is false: confirm the wording with the user first. To record an incident internally and page… | writes |
add_status_page_incident_updatePost status page incident update | Post an update on a status page incident (investigating, identified, update, monitoring, resolved). Public, and sent to subscribers unless notify_subscribers is false. | writes |
resolve_status_page_incidentResolve status page incident | Close a status page incident with a final "resolved" update. Same as add_status_page_incident_update with status "resolved"; refuses an incident that is already resolved. | writes |
update_status_page_incidentEdit status page incident | Change a status page incident's title, type, status pages or affected services. The pages show the change right away; subscribers are not notified. To tell them something, post an update. | writes |
edit_status_page_incident_updateCorrect status page incident update | Correct the text or stage of an update already posted, e.g. a typo. The page shows the correction; subscribers are not notified again and its date is kept. | writes |
list_maintenance_windowsList maintenance windows | Maintenance windows, 20 per page, with their monitors, status pages, updates and status (upcoming, inprogress, completed). | read-only |
get_maintenance_windowGet maintenance window | One maintenance window with its updates and the state of its subscriber notification. | read-only |
create_maintenance_windowSchedule maintenance | Schedule a maintenance window: checks and alerts stop for its monitors during the window, and the status pages you pass announce it. Public once it has status pages: confirm with the user first. | writes |
update_maintenance_windowUpdate maintenance | Reschedule a maintenance window, rename it, change its monitors or status pages, or post a public update on it. The pages show the change; subscribers are not notified. | writes |
complete_maintenance_windowEnd maintenance now | End a maintenance window in progress now: checks and alerts resume on its monitors and the status pages show it as completed. | writes |
cancel_maintenance_windowCancel maintenance | Cancel a maintenance window that has not started: it is deleted and leaves the status pages. Subscribers already told about it are not told it is cancelled. To end one in progress, use complete_maintenance_window. | writes |
search_logsSearch logs | Search the project's logs, newest first. Logs search language (not SQL): free words are ANDed (whole words), "exact phrase", -word to exclude, service:api, host:web-1, env:prod, source:src_…, level:error or… | read-only |
get_outage_logsGet outage logs | Logs around one outage (incident) of the project: from 15 min before it started to 5 min after it ended. Returns warnings and errors grouped by message pattern, the latest matching lines, and a per-level histogram.… | read-only |
summarize_log_errorsSummarize log errors | Groups the project's errors (or warnings) of a time window by message pattern (numbers, ids and IPs normalized), most frequent first: count, share, trend (>1 = rising in the last quarter of the window), level, services,… | read-only |
list_log_dashboardsList log dashboards | Log dashboards of the project: name, tags, widget count, template, last update. With `uuid`, one dashboard in detail: its time range, variables, sections and every widget with its chart as HPL (run one with… | read-only |
run_log_chartRun a log chart | Aggregates the project's logs into a chart and returns a compact summary: per series min/max/avg/last and up to `max_points` points, a table (up to 50 rows) or a single value. HPL = `<search> | <aggregations> [by… | read-only |
create_log_dashboard_from_templateCreate a log dashboard from a template | Creates a log dashboard from a ready-made template (overview, errors-patterns, http-access, app-otel, containers, host-syslog, databases, jobs, ingestion-cost, incident-war-room, vercel). The template's fields (HTTP… | writes |
get_outage_checksCompare an outage across regions | Region-by-region evidence for one outage ("outage_…" or an incident key like "INC-12"): a verdict — "global" (every checked region failed), "partial" (some regions stayed healthy, listed), "single_region" or "unknown"… | read-only |
find_correlated_outagesFind correlated outages | Other incidents of this project that started within ±window_minutes (default 10, max 60) of an outage (outage_uuid, or incident key) or of a moment (at), each with monitor (uuid, name), start, end or ongoing, status… | read-only |
get_recent_changesRecent changes before an incident | What changed on a monitor before a moment (default: the outage start) and shortly after: audit-log changes to the monitor and to its escalation policies (regions, URL, timeout, pause / resume..., with who made them;… | read-only |
run_check_nowRun a check now from every region | Run the monitor's check right now from each of its regions (20 at most) and return per region: ok, status, total ms, error, failure layer and phase timings in integer ms (dns, connect, ttfb, download), once every region… | read-only |
list_healthchecksList healthchecks | Cron/heartbeat healthchecks of the project (jobs that ping Hyperping; monitors are list_monitors, servers list_servers): per healthcheck its hc_ uuid, name, schedule (cron + timezone, or period), grace period, state… | read-only |
get_healthcheckGet healthcheck | One healthcheck in detail: schedule, grace, state and timing, escalation policy, uptime and downtime over the last 30 days, its last 20 pings (pings are kept 15 days; "start" = a /start ping without its completion) and… | read-only |
list_serversList servers | Servers of the project (machines running the Hyperping agent, agt_ uuids; not monitors or healthchecks): per server its name, hostname, status (online, stale = heartbeat late, offline, uninstalled), last_seen_at, OS,… | read-only |
get_serverGet server | One server in detail: status, last seen, OS, agent version (and whether an update exists), hardware, group, tags, escalation policy; current memory and root disk usage; last 24 h of CPU %, memory %, disk % (all… | read-only |
list_audit_logList audit log | Who changed what in the project (the Audit Log page; owners and admins, Business plan): newest first, each event with its time, actor (user name and email, or the API key / MCP key that acted, or system), action (e.g.… | read-only |
get_project_reportProject uptime report | Uptime of every monitor of the project over a period, worst first, in one call: per monitor uptime_pct, downtime (seconds + text), outage count, longest outage and MTTR (mean time to resolve, resolved outages only),… | read-only |
get_outage_alertsGet outage alert deliveries | Who was notified for one outage, and how: every alert delivery attempt (time, channel email/sms/phonecall/slack/teams/webhook/pagerduty/opsgenie/…, recipient: user name and email, phone as its last 4 digits, or the… | read-only |
What https://api.hyperping.io/v1/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 3 warnings · 1 note
- warnTC11update_status_page3 parameters without a description: font, hide_from_search_engines, theme
- warnTC21get_monitor_mttrdescribed almost the same as get_monitor_mtta (80% of the same words)
- warnTC23server67 tools, about 18,180 tokens of definitions
- noteTC24server67 of 67 tools have no outputSchema
The checks from /check and anchor check, run each day on the list above: about 18,757 tokens of definitions. Not part of the score yet. Check your own server.