com.hyperping/hyperping
REMOTE · API.HYPERPING.IO · SCANNED SEP 20
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2708 tokens (~104/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.hyperping/hyperping MCP server?
com.hyperping/hyperping is a hosted endpoint at https://api.hyperping.io/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.hyperping.io
claude mcp add --transport http com-hyperping-hyperping 'https://api.hyperping.io/v1/mcp'
{
"mcpServers": {
"com-hyperping-hyperping": {
"url": "https://api.hyperping.io/v1/mcp"
}
}
} {
"servers": {
"com-hyperping-hyperping": {
"type": "http",
"url": "https://api.hyperping.io/v1/mcp"
}
}
} [mcp_servers.com-hyperping-hyperping] url = "https://api.hyperping.io/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hyperping-hyperping": {
"type": "remote",
"url": "https://api.hyperping.io/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-hyperping-hyperping --url 'https://api.hyperping.io/v1/mcp' --transport streamable-http
mcp_servers:
com-hyperping-hyperping:
url: "https://api.hyperping.io/v1/mcp" {
"McpServers": {
"com-hyperping-hyperping": {
"Transport": "http",
"Url": "https://api.hyperping.io/v1/mcp"
}
}
} assistant mcp add com-hyperping-hyperping -t streamable-http -u 'https://api.hyperping.io/v1/mcp'
{
"mcpServers": {
"com-hyperping-hyperping": {
"type": "http",
"url": "https://api.hyperping.io/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 0
- Tool “get_monitor_mtta” rewrote its description, which is the text the model reads security
- Tool “get_monitor_mttr” rewrote its description, which is the text the model reads security
- Tool “get_monitor_response_time” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_monitor_mtta” reworded the description of “monitor_uuids” cosmetic
- “get_monitor_mttr” reworded the description of “monitor_uuids” cosmetic
- “get_monitor_response_time” reworded the description of “monitor_uuids” cosmetic
- “get_monitor_uptime” reworded the description of “monitor_uuids” cosmetic
- 30 Aug 26 +1
- Stability: 0.97 → pass security
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.hyperping.io/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hyperping.io | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 130b484642b7a0730e799785c93e4e7b |
| SANs: hyperping.io, *.hyperping.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.hyperping.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| hyperping.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.hyperping.io/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.hyperping.io/v1/mcp | HTTPS enforced | 301 | https://api.hyperping.io/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_monitor Create monitor ~369
Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.
| Name | Type | Req | Description |
|---|---|---|---|
| alerts_wait | number | – | Minutes to wait before alerting. -1 disables, 0 is immediate. |
| check_frequency | number | – | Check interval in seconds. Sub-30s requires a business plan. |
| dns_expected_answer | string | – | Expected DNS answer to assert against. |
| dns_nameserver | string | – | Custom nameserver for DNS checks. |
| dns_record_type | string | – | DNS record type (protocol="dns"). |
| escalation_policy | string | – | UUID of an escalation policy to link. |
| expected_status_code | string|number | – | Expected response status: number (200), "2xx", or "1xx-3xx". |
| follow_redirects | boolean | – | Follow 3xx redirects on http monitors. |
| group_id | – | – | Group to place the monitor in. |
| http_method | string | – | HTTP verb. Defaults to GET. |
| name | string | yes | Human-readable monitor name. |
| paused | boolean | – | Start the monitor in a paused state. |
| port | integer | – | TCP port — required when protocol is "port". |
| protocol | string | – | Check protocol. Defaults to "http". |
| regions | array | – | Probe region codes, e.g. ["us-east","eu-west"]. Use ["*"] for all. |
| request_body | string | – | Body for http requests. |
| request_headers | array | – | Custom request headers. |
| required_keyword | string | – | Body must contain this keyword, else flagged down. |
| timeout | integer | – | Request timeout in seconds (default 30). |
| url | string | yes | Target URL (http) or hostname (icmp/port/dns). |
No output schema declared.
No examples provided.
get_escalation_policy Get escalation policy ~46
One policy by UUID. Reveals step sequence, linked schedules, and contact channels.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Escalation policy UUID (format "esc_..."). |
No output schema declared.
No examples provided.
get_integration Get integration ~45
One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Integration UUID (format "int_..."). |
No output schema declared.
No examples provided.
get_monitor Get monitor ~30
Fetch a single monitor by its UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Monitor UUID (format "mon_...") |
No output schema declared.
No examples provided.
get_monitor_anomalies Get monitor anomalies ~44
Anomaly-detection output for a single monitor (flapping, latency spikes, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Monitor UUID (format "mon_..."). |
No output schema declared.
No examples provided.
get_monitor_http_logs Get monitor HTTP logs ~87
Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures.
| Name | Type | Req | Description |
|---|---|---|---|
| level | array | – | Filter by log level. |
| limit | integer | – | Rows per page. Default 50, max 200. |
| page | integer | – | Zero-indexed page. Default 0. |
| uuid | string | yes | Monitor UUID (format "mon_..."). |
No output schema declared.
No examples provided.
get_monitor_mtta Get MTTA per monitor ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO start date. Default: 30 days ago. |
| monitor_uuids | array | – | Monitor UUIDs to report on. Pass EVERY monitor you care about in a SINGLE call: the endpoint resolves them in one aggregate query and returns a per-monitor breakdown, so N monitors in one call costs… |
| to | string | – | ISO end date. Default: now. |
No output schema declared.
No examples provided.
get_monitor_mttr Get MTTR per monitor ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO start date. Default: 30 days ago. |
| monitor_uuids | array | – | Monitor UUIDs to report on. Pass EVERY monitor you care about in a SINGLE call: the endpoint resolves them in one aggregate query and returns a per-monitor breakdown, so N monitors in one call costs… |
| to | string | – | ISO end date. Default: now. |
No output schema declared.
No examples provided.
get_monitor_outages Get outages for a monitor ~79
Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_uuid | string | yes | Monitor UUID (format "mon_...") to filter by. |
| page | integer | – | Zero-indexed page number, 20 per page. |
| status | string | – | Filter by status. Defaults to "all". |
No output schema declared.
No examples provided.
get_monitor_response_time Get response time ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO start date. Default: 30 days ago. |
| monitor_uuids | array | – | Monitor UUIDs to report on. Pass EVERY monitor you care about in a SINGLE call: the endpoint resolves them in one aggregate query and returns a per-monitor breakdown, so N monitors in one call costs… |
| resolution | string | – | Time grouping. Default "day". |
| to | string | – | ISO end date. Default: now. |
No output schema declared.
No examples provided.
get_monitor_uptime Get uptime (SLA) stats ~156
Uptime percentage over a date window, aggregated and optionally per day/hour/week/month.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO start date. Default: 30 days ago. |
| monitor_uuids | array | – | Monitor UUIDs to report on. Pass EVERY monitor you care about in a SINGLE call: the endpoint resolves them in one aggregate query and returns a per-monitor breakdown, so N monitors in one call costs… |
| resolution | string | – | Time grouping. Default "day". |
| to | string | – | ISO end date. Default: now. |
No output schema declared.
No examples provided.
get_on_call_schedule Get on-call schedule ~39
One schedule by UUID with full rotation detail and the linked escalation policies.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Schedule UUID (format "sch_..."). |
No output schema declared.
No examples provided.
get_outage Get outage ~36
Fetch a single outage by UUID, including acknowledgements, description, and root cause.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Outage UUID. |
No output schema declared.
No examples provided.
get_outage_timeline Get outage timeline ~54
Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Outage UUID (format "outage_..." or "INC-123"). |
No output schema declared.
No examples provided.
get_status_summary Status summary ~28
Up/down/paused counts plus a list of currently down monitors with the timestamp they went down.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_escalation_policies List escalation policies ~28
All escalation policies in the project. Use to find which monitors route alerts where.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_integrations List integrations ~35
All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_monitors List monitors ~85
Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows per page. Default 50, max 200. |
| page | integer | – | Zero-indexed page. Default 0. |
| status | string | – | Filter by state. "ssl_expiring" = SSL expires within 30 days. |
No output schema declared.
No examples provided.
list_on_call_schedules List on-call schedules ~30
All on-call schedules in the project. Each entry typically includes rotation config and current on-call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_outages List outages ~97
Paginated list of outages in the project. Filter by status, type, or search term.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Zero-indexed page number, 20 outages per page. |
| search | string | – | Substring matched against monitor name/URL/domain or "INC-123". |
| status | string | – | Filter by status. Defaults to "all". |
| type | string | – | Filter by type. Defaults to "all". |
No output schema declared.
No examples provided.
list_recent_alerts List recent alerts ~90
Alert notifications (up/down transitions) over a date range. Defaults to last 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO start date. Default: 30 days ago. |
| monitor_uuids | array | – | Restrict to these monitor UUIDs. |
| resolution | string | – | Time grouping. Default "day". |
| to | string | – | ISO end date. Default: now. |
No output schema declared.
No examples provided.
list_team_members List team members ~29
Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_monitor Pause monitor ~41
Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | UUID of the monitor to pause. |
No output schema declared.
No examples provided.
resume_monitor Resume monitor ~34
Resume a paused monitor. Same as update_monitor with paused=false.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | UUID of the monitor to resume. |
No output schema declared.
No examples provided.
search_monitors_by_name Search monitors by name ~39
Case-insensitive substring search across monitor names and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Case-insensitive substring matched against monitor names or URLs. |
No output schema declared.
No examples provided.
update_monitor Update monitor ~372
Patch a monitor. Pass only fields you want to change; others are preserved.
| Name | Type | Req | Description |
|---|---|---|---|
| alerts_wait | number | – | Minutes to wait before alerting. -1 disables, 0 is immediate. |
| check_frequency | number | – | Check interval in seconds. Sub-30s requires a business plan. |
| dns_expected_answer | string | – | Expected DNS answer to assert against. |
| dns_nameserver | string | – | Custom nameserver for DNS checks. |
| dns_record_type | string | – | DNS record type (protocol="dns"). |
| escalation_policy | string | – | UUID of an escalation policy to link. |
| expected_status_code | string|number | – | Expected response status: number (200), "2xx", or "1xx-3xx". |
| follow_redirects | boolean | – | Follow 3xx redirects on http monitors. |
| group_id | – | – | Group to place the monitor in. |
| http_method | string | – | HTTP verb. Defaults to GET. |
| name | string | – | Human-readable monitor name. |
| paused | boolean | – | Start the monitor in a paused state. |
| port | integer | – | TCP port — required when protocol is "port". |
| protocol | string | – | Check protocol. Defaults to "http". |
| regions | array | – | Probe region codes, e.g. ["us-east","eu-west"]. Use ["*"] for all. |
| request_body | string | – | Body for http requests. |
| request_headers | array | – | Custom request headers. |
| required_keyword | string | – | Body must contain this keyword, else flagged down. |
| timeout | integer | – | Request timeout in seconds (default 30). |
| url | string | – | Target URL (http) or hostname (icmp/port/dns). |
| uuid | string | yes | UUID of the monitor to update. |
No output schema declared.
No examples provided.
What is the com.hyperping/hyperping MCP server?
com.hyperping/hyperping is an MCP server listed in the public MCP registry as com.hyperping/hyperping. Uptime, API and server monitoring with outages, reporting, on-call and status pages. This page covers its hosted endpoint (https://api.hyperping.io/v1/mcp).
Is the com.hyperping/hyperping MCP server safe to use?
com.hyperping/hyperping scores 90 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.hyperping/hyperping MCP server expose?
com.hyperping/hyperping exposes 26 tools: list_monitors, get_monitor, create_monitor, update_monitor, pause_monitor, and 21 more. Their descriptions and schemas cost roughly 2,397 tokens of context every time the server is loaded.
Does the com.hyperping/hyperping MCP server require authentication?
Yes. com.hyperping/hyperping asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.hyperping/hyperping MCP server still maintained?
com.hyperping/hyperping is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.