MCP.Market

Hyperping MCP server

online · 100% uptime
by hyperping.com·com.hyperping/hyperping·v1.0.0·1 stars
No reviews yet

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Hyperping yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Hyperping tools (26, 2 write)

write = sends, deletes, buys or posts
  • create_monitorwrite actionFree

    Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.

  • get_escalation_policyFree

    One policy by UUID. Reveals step sequence, linked schedules, and contact channels.

  • get_integrationFree

    One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.).

  • get_monitorFree

    Fetch a single monitor by its UUID.

  • get_monitor_anomaliesFree

    Anomaly-detection output for a single monitor (flapping, latency spikes, etc.).

  • get_monitor_http_logsFree

    Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures.

  • get_monitor_mttaFree

    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.

  • get_monitor_mttrFree

    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.

  • get_monitor_outagesFree

    Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages.

  • get_monitor_response_timeFree

    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.

  • get_monitor_uptimeFree

    Uptime percentage over a date window, aggregated and optionally per day/hour/week/month.

  • get_on_call_scheduleFree

    One schedule by UUID with full rotation detail and the linked escalation policies.

  • get_outageFree

    Fetch a single outage by UUID, including acknowledgements, description, and root cause.

  • get_outage_timelineFree

    Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.

  • get_status_summaryFree

    Up/down/paused counts plus a list of currently down monitors with the timestamp they went down.

  • list_escalation_policiesFree

    All escalation policies in the project. Use to find which monitors route alerts where.

  • list_integrationsFree

    All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).

  • list_monitorsFree

    Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).

  • list_on_call_schedulesFree

    All on-call schedules in the project. Each entry typically includes rotation config and current on-call.

  • list_outagesFree

    Paginated list of outages in the project. Filter by status, type, or search term.

  • list_recent_alertsFree

    Alert notifications (up/down transitions) over a date range. Defaults to last 30 days.

  • list_team_membersFree

    Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.

  • pause_monitorFree

    Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.

  • resume_monitorFree

    Resume a paused monitor. Same as update_monitor with paused=false.

  • search_monitors_by_nameFree

    Case-insensitive substring search across monitor names and URLs.

  • update_monitorwrite actionFree

    Patch a monitor. Pass only fields you want to change; others are preserved.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 986ms20/20
  • Tool poisoning26 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 56 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Hyperping compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Tools
26
the typical server has 7
Tools that change things
8%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
118 ms
faster than 80% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 24 read · 1 create · 1 change

Install Hyperping in Claude Code, Cursor or VS Code

claude mcp add --transport http hyperping https://api.hyperping.io/v1/mcp
Add to Cursor

What the publisher says

From the Hyperping repository's README, as published. We do not edit it. Read it on GitHub

Hyperping MCP Server

Official Model Context Protocol server for Hyperping. It exposes uptime monitoring, incident history, on-call schedules and reporting to AI agents over HTTP.

This is a remote server. There is nothing to install or self-host: point your client at the endpoint with an API key. This repository holds the registry manifest, the client configuration and the tool reference.

Full documentation: hyperping.com/docs/mcp

Endpoint

Quick start

  1. In Hyperping, go to Project Settings, API Keys and create a readonly or readwrite key.
  2. Add the server to your MCP client (see below).
  3. Restart the client, then ask it things like "what is down right now?" or "what was our uptime on the API monitor last month?"

Claude Desktop, Claude Code, Cursor, Windsurf

{
  "mcpServers": {
    "hyperping": {
      "type": "http",
      "url": "https://api.hyperping.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer sk_..."
      }
    }
  }
}

stdio clients

Clients that only speak stdio can bridge through mcp-remote:

{
  "mcpServers": {
    "hyperping": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.hyperping.io/v1/mcp",
        "--header",
        "Authorization: Bearer sk_..."
      ]
    }
  }
}

Tools

Monitors

delete_monitor is deliberately not exposed. Use the dashboard or the REST API.

Status and outages

Reporting

Diagnostics

On-call

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Hyperping: common questions

Is Hyperping MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Hyperping safety report
How do I install Hyperping?
It runs remotely at api.hyperping.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Hyperping need an API key?
Yes. The registry entry asks for Authorization.
Is Hyperping maintained?
The last commit was 97 days ago (2026-07-30). The latest release is v1.0.0.
Is Hyperping up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Hyperping?
Servers from other publishers that do the same job: OneUptime MCP server.
How does Hyperping compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); tools 26 (the typical server has 7); tools that change things 8% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Hyperping

Same job from other publishers: the closest match first, then the best rated.

  • OneUptime
    Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
    A