Skip to content
LiciumTalk to usFor agentsSign in

MCP server list / hyperping

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

Answered:

4 of 4 checks

Status
responds
Typical response time
537 ms
Last checked
Latest check:
This server answered at its latest check.Last checked  · MCP initialize · 8s limit · HTTP 200 · answered in 246 ms.
Address
https://api.hyperping.io/v1/mcp
Listed in:
official MCP registry mcp_registry
Registry name
com.hyperping/hyperping
Transport
streamable HTTP streamable-http
Host
api.hyperping.io

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

What the server says about itself

We have not checked it.
Server name:
hyperping-monitors
Version:
1.0.0
MCP features it lists:
tools
Tool names:
list_monitorsget_monitorcreate_monitorupdate_monitorpause_monitorresume_monitorsearch_monitors_by_nameget_status_summarylist_outagesget_outageget_outage_timelineget_monitor_outages
and 14 morelist_recent_alertsget_monitor_uptimeget_monitor_response_timeget_monitor_mttrget_monitor_mttaget_monitor_anomaliesget_monitor_http_logslist_on_call_schedulesget_on_call_schedulelist_escalation_policiesget_escalation_policylist_team_memberslist_integrationsget_integration
Instructions excerpt:
Hyperping synthetic-monitoring tools, scoped to the authenticated project. RATE LIMITS per project. Per minute: initialize=5, tools/list=30, tools/call=60. Per hour: initialize=20, tools/list=200, tools/call=600. BOTH windows apply — slowing down within a minute is not enough if you exceed the hourly cap. Exceeding any of these returns a JSON-RPC error wit…

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

oldest to newest; each row is one recorded check
Recorded checks for hyperping
CheckedStatusTookCheck
responds375 msMCP initialize · 8s limit · HTTP 200
responds744 msMCP initialize · 8s limit · HTTP 200
responds699 msMCP initialize · 8s limit · HTTP 200
responds246 msMCP initialize · 8s limit · HTTP 200

Need a different server, page or part?

Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.