Hyperping
Monitor website uptime, API health, and server status with alerts and reporting.
Connects to Hyperping uptime monitoring to check website and API availability across regions, track outages, view response times and uptime metrics, manage on-call schedules, and route alerts to Slack, Teams, PagerDuty and other channels.
Try asking Muse: "Show me which of my websites are currently down and when they went offline."
Source: Found in the official MCP Registry (com.hyperping/hyperping) · First listed September 24, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 36 min ago.
Is it safe to connect?
What Muse can see: You sign in to your own account with it, so Muse can reach what that account allows. Read what it asks for before you agree.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://api.hyperping.io/v1/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 45ms. Worked in 100% of checks over 30 days.
Screening · September 24, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 40
list_monitorsPaginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).get_monitorFetch a single monitor by its UUID.create_monitorCreate a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.update_monitorPatch a monitor. Pass only fields you want to change; others are preserved.pause_monitorPause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.resume_monitorResume a paused monitor. Same as update_monitor with paused=false.search_monitors_by_nameCase-insensitive substring search across monitor names and URLs.get_status_summaryUp/down/paused counts plus a list of currently down monitors with the timestamp they went down.list_outagesPaginated list of outages in the project. Filter by status, type, or search term.get_outageFetch a single outage by UUID, including acknowledgements, description, and root cause.get_outage_timelineFull activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.get_monitor_outagesPaginated list of outages scoped to one monitor. Convenience wrapper around list_outages.create_outageDeclare 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 status page (create_status_page_incident does that).acknowledge_outageMark an ongoing outage as being handled: repeat alerts stop. Escalation steps still fire on schedule; resolve it or fix the cause to stop them.escalate_outagePage the next step of the outage's escalation policy now instead of waiting for it. Each call moves one step further.resolve_outageResolve 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.list_recent_alertsAlert notifications (up/down transitions) over a date range. Defaults to last 30 days.get_monitor_uptimeUptime percentage over a date window, aggregated and optionally per day/hour/week/month.get_monitor_response_timeResponse 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.get_monitor_mttrMean 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.get_monitor_mttaMean 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.get_monitor_anomaliesAnomaly-detection output for a single monitor (flapping, latency spikes, etc.).get_monitor_http_logsRecent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures.list_on_call_schedulesAll on-call schedules in the project. Each entry typically includes rotation config and current on-call.get_on_call_scheduleOne schedule by UUID with full rotation detail and the linked escalation policies.list_escalation_policiesAll escalation policies in the project. Use to find which monitors route alerts where.get_escalation_policyOne policy by UUID. Reveals step sequence, linked schedules, and contact channels.list_team_membersUsers on the project, with names and emails. Use to resolve user IDs from schedules/policies.list_integrationsAll notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).get_integrationOne integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.).list_status_pagesStatus pages in the project, 20 per page: UUID, name, public URL, password protection.get_status_pageOne status page with its settings (languages, subscriptions, access) and the services it shows, section by section, with their UUIDs.create_status_pageCreate a status page on a hyperping.app subdomain, with sections of monitors and components. It is public as soon as it exists: confirm the name, address and services with the user first. Password protection, SSO, a custom domain and a logo are set in the dashboard.update_status_pageChange 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.add_status_page_servicesShow monitors or components 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.remove_status_page_servicesTake monitors or components off a status page, wherever they appear, groups included. Their settings on the page (display name, description) are lost.list_status_page_incidentsIncidents published on status pages, newest first, each with its current stage and latest update. For downtime detected on monitors, use list_outages.get_status_page_incidentOne status page incident with every update (newest first, with their UUIDs), its status pages and affected components.create_status_page_incidentPublish 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 on-call instead, use create_outage.add_status_page_incident_updatePost an update on a status page incident (investigating, identified, update, monitoring, resolved). Public, and sent to subscribers unless notify_subscribers is false.Recent checks
Link
https://api.hyperping.io/v1/mcpQuestions about Hyperping in Muse
How do I connect Hyperping to Muse?
Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Hyperping to help me. It is a free service with an MCP server at https://api.hyperping.io/v1/mcp. It needs an API key from Hyperping; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
Is Hyperping working right now?
At the last check (September 28, 2026, 08:31 UTC) the endpoint was working, answering in 45ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
Is Hyperping safe to connect to Muse?
It was screened on September 24, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can Hyperping do in Muse?
It exposes 40 tools, including list_monitors, get_monitor, create_monitor, update_monitor. For example, you could ask Muse: "Show me which of my websites are currently down and when they went offline."
Follow Hyperping
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (com.hyperping/hyperping)). If you build Hyperping, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/hyperping"><img src="https://musedirectory.ai/badge/hyperping.svg" alt="Hyperping on musedirectory.ai" width="236" height="40"></a>