The Hyperping MCP server gives Claude, Cursor, Codex and any MCP client live access to your monitors, outages, uptime, on-call and status pages. Ask in plain words, or let it create monitors and post incidents for you.
On Essentials, Pro and Business. Nothing to install.
What’s down right now?
get_status_summary()get_outage_timeline(uuid: "out_8f2c")2 of your 48 monitors are down.
2 down · 46 up
Checkout went down at 14:02 UTC, confirmed from London, Frankfurt and Virginia. Sarah acknowledged it two minutes later. Want the full timeline?
“Why is checkout down?” brings back the timeline: detection, confirmation from other regions, alerts sent and who acknowledged. Follow-ups drill into the probe logs.
Your agent drafts the incident from what your monitors saw and publishes it on your status page once you approve the wording. Updates and the resolution follow the same way, and subscribers get each one.
Deploying a new endpoint? Your coding agent adds its monitor, regions and escalation policy in the same session as the code.
Uptime, response times, MTTR and MTTA per monitor over any window, ready for a weekly digest or a customer’s SLA review.
Schedule the window and announce it on your status page, with a heads-up to subscribers. Checks and alerts stop for the monitors involved, then start again on their own.
Impact window, time to acknowledge and every alert sent, per channel: the facts of the incident, pulled into a first draft.
list_monitorsFilter by up, down, paused or SSL expiring.get_monitorOne monitor with its full configuration.search_monitors_by_nameFind monitors by name or URL.create_monitorwriteHTTP, ping, port or DNS checks.update_monitorwriteChange any setting of a monitor.pause_monitorwriteStop checks and alerts, keep history.resume_monitorwriteStart checking again.get_status_summaryWhat’s up, what’s down, since when.get_monitor_uptimeSLA over any window, per day to month.get_monitor_response_timeLatency trend per monitor.get_monitor_mttrMean time to resolve.get_monitor_mttaMean time to acknowledge.list_outagesEvery outage, searchable and filtered.get_outageOne outage and its details.get_outage_timelineDetection to resolution, step by step.get_monitor_outagesThe outages of one monitor.get_monitor_anomaliesFlapping and latency spikes.get_monitor_http_logsRecent probe logs.list_recent_alertsAlerts sent, across every channel.list_on_call_schedulesEvery rotation.get_on_call_scheduleOne rotation and its overrides.list_escalation_policiesEvery escalation chain.get_escalation_policyOne policy, step by step.list_team_membersNames and emails of your team.list_integrationsSlack, Teams, PagerDuty, webhooks…get_integrationOne channel and its settings.list_status_pagesEvery page, its URL and its access.get_status_pageIts languages, subscriptions and services.list_incidentsOngoing and resolved, newest first.get_incidentOne incident and every update.create_incidentwritePublish it and notify subscribers.add_incident_updatewriteIdentified, monitoring or a new update.resolve_incidentwriteClose it with a final update.list_maintenance_windowsUpcoming, ongoing and past windows.get_maintenance_windowOne window and its announcement.create_maintenance_windowwriteSchedule it, announce it, pause checks.In Hyperping, open Project settings → API keys. Pick read-only for agents that only need to look, read and write for the ones that act.
One URL and one header. Pick your client for the exact command or file, or paste the JSON into any MCP client.
“What’s down right now?” is a good first question. Your agent picks the tools, Hyperping returns the facts.
claude mcp add --transport http hyperping \
https://api.hyperping.io/v1/mcp \
--header "Authorization: Bearer $HYPERPING_API_KEY"Each API key belongs to a single project. Anything outside it returns a 404, even with a valid ID.
Give agents you don’t fully trust a read-only key. Write tools refuse it in the server, so no prompt can talk its way around it.
Agents can create and change monitors, incidents and maintenance windows, never delete them. Deletion stays in the dashboard and the REST API.
Delete a key in the dashboard and the next call fails. Keys can also expire on their own, from one hour to one year.
Limits apply per project and come back as a clear error with the seconds to wait, so a looping agent slows down instead of failing silently.
A hosted server over streamable HTTP. No local process, no package to keep up to date, the same API keys as the REST API.
USD · Monthly billing for every plan
Three subscriptions to keep it all running.
$747/month
$8,964 over 12 months
Everything connected, from the first check.
$299/month
$3,588 over 12 monthsSave $5,376 a year with this mix.
Reviewed . All amounts are USD; local currency prices may differ.
This is one example of a three-tool stack, not the cheapest possible setup or a feature-for-feature match. Pingdom and PagerDuty also include status-page features; a separate Statuspage subscription may not be needed by every team. Usage charges and paid connectors are not included. Annual totals are 12 monthly payments, not annual subscription quotes.
A hosted Model Context Protocol server at https://api.hyperping.io/v1/mcp. It exposes a Hyperping project to AI agents as 36 tools: 28 read tools for monitors, outages, alerts, uptime, response times, MTTR, MTTA, on-call, integrations, status pages, incidents and maintenance windows, and 8 write tools to manage monitors, publish and resolve status page incidents, and schedule maintenance. See the tool reference.
Any MCP client that connects to remote servers over streamable HTTP with a custom header: Claude Code, Cursor, OpenAI Codex, VS Code with GitHub Copilot, Windsurf, Gemini CLI and Zed. Clients that only run local servers, such as Claude Desktop, connect through the mcp-remote bridge. The agent setup guide has the configuration for each.
The MCP server uses API keys, available on the Essentials, Pro and Business plans. MCP calls cost nothing extra. See pricing.
With a Hyperping API key sent as an Authorization: Bearer header. Each key belongs to one project and is either read-only or read and write. OAuth sign-in is not supported yet: clients that only offer OAuth connect through the mcp-remote bridge.
No. Deletion is not exposed over MCP. An agent with a read and write key can create, update, pause and resume monitors, publish incidents and schedule maintenance, but deleting any of them takes the dashboard or the REST API. A read-only key cannot change anything.
Yes, with a read and write key. It can publish an incident, post its updates, resolve it and schedule maintenance, and subscribers are notified as when you post from the dashboard, unless the agent turns notifications off. The server asks agents to show you the exact text before publishing, and a read-only key cannot publish anything.
Per project, 60 tool calls a minute and 600 an hour. Calls also count toward the project’s REST API quota. Past a limit, the server returns an error that says how many seconds to wait.
Yes. /docs/llms.txt indexes every page, every page has a Markdown version at its URL followed by index.md, and /mcp/llms.txt describes every MCP tool with its parameters and common queries.
