pingpulse

pingpulse is a small local bridge to the hosted Hyperping uptime-monitoring MCP server. It puts the whole monitoring workspace behind one tool surface: the monitors watching your sites and APIs, the outages they produce, the people who get woken up when something breaks, and the public status pages that tell your users what is happening.

From here an agent can list and inspect monitors, pause or resume them, run a check on demand, read uptime, response-time, MTTR and MTTA figures, work through outages (acknowledge, escalate, resolve), review on-call schedules and escalation policies, manage status pages and post or update their incidents, schedule maintenance windows, search logs and log dashboards, and pull project reports, healthchecks, servers, browser runs and the audit log. The surface is 69 tools, exactly as captured from the live endpoint. No payment, billing or plan tool exists in it.

The bridge holds no monitoring data of its own. It answers the tool list locally, exactly as captured, and forwards each tool call upstream, returning whatever comes back untouched.

Tools

Grouped by area; required arguments are listed where the captured schema carries them. Tools not listed with required arguments take none that are required (26 of the 69 carry no required key at all in the capture, and they are served that way).

• Monitors: list_monitors, get_monitor (uuid), create_monitor (name, url), update_monitor (uuid), pause_monitor (uuid), resume_monitor (uuid), search_monitors_by_name (query), get_status_summary.
• Outages and alerts: list_outages, get_outage (uuid), get_outage_timeline (uuid), get_monitor_outages (monitor_uuid), create_outage (description), acknowledge_outage (uuid), escalate_outage (uuid), resolve_outage (uuid), list_recent_alerts, get_outage_alerts (uuid).
• Monitor metrics: get_monitor_uptime, get_monitor_response_time, get_monitor_mttr, get_monitor_mtta, get_monitor_anomalies (uuid), get_monitor_http_logs (uuid).
• On-call: list_on_call_schedules, get_on_call_schedule (uuid), list_escalation_policies, get_escalation_policy (uuid), list_team_members, get_on_call_now.
• Integrations: list_integrations, get_integration (uuid).
• Status pages: list_status_pages, get_status_page (uuid), create_status_page (name, subdomain), update_status_page (uuid), add_status_page_services (uuid, services), remove_status_page_services (uuid, services).
• Status page incidents: list_status_page_incidents, get_status_page_incident (uuid), create_status_page_incident (title, message, status_pages), add_status_page_incident_update (uuid, message, status), resolve_status_page_incident (uuid, message), update_status_page_incident (uuid), edit_status_page_incident_update (uuid, update_uuid).
• Maintenance: list_maintenance_windows, get_maintenance_window (uuid), create_maintenance_window (name, start_date, end_date, monitors), update_maintenance_window (uuid), complete_maintenance_window (uuid), cancel_maintenance_window (uuid).
• Logs: search_logs, get_outage_logs (uuid), summarize_log_errors, list_log_dashboards, run_log_chart, create_log_dashboard_from_template (template_id).
• Checks and changes: get_outage_checks (uuid), find_correlated_outages, get_recent_changes, run_check_now (uuid).
• Platform views: list_healthchecks, get_healthcheck (uuid), list_servers, get_server (uuid), list_audit_log, get_project_report, list_browser_runs (uuid), get_browser_run (uuid).

Configuration

• HYPERPING_MCP_URL (optional) — override the upstream endpoint. Defaults to https://api.hyperping.io/v1/mcp. (The override hook is this rebuild's own labelled reconstruction.)
• `HYPERPING

... View full README on GitHub