mcp server
com.hyperping/hyperping
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Description as published by the maintainer. Source
- version 1.0.0
- active
- analytics
active — Most recent push to the repository was 2026-07-30. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-30 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-29 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-29 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
DebugBundle
— last commit 2026-07-29, shares incident-management, observability
DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.
-
FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe
— last commit 2026-08-06, shares observability, on-call
FastMCP server that pages on-call via 100+ notification channels (Apprise wrapper)
-
io.github.cyanheads/devops-status-mcp-server
— last commit 2026-07-31, shares monitoring, sre
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
-
io.github.Areso/safe-ssh-mcp
— last commit 2026-06-04, shares observability, sre
A secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands
-
Servonaut
— last commit 2026-08-05, shares sre
Manage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec.
-
io.github.arnavranjan005/mcp-telemetry-server
— last commit 2026-07-29, shares monitoring, observability
Streams live progress from mcp-telemetry-sdk-instrumented tools to any connected MCP client.
-
World Monitor
— last commit 2026-08-06, shares monitoring
Live global intelligence: real-time markets, conflicts, country risk, chokepoints, energy. 39 tools.
-
com.clauxel.agentmonitorrelay/agentmonitorrelay-mcp
— last commit 2026-05-19, shares monitoring
AI agent run monitoring with incident replay and SLA receipts.
-
com.scoutapm/scout-mcp-local
— last commit 2026-06-20, shares monitoring
An MCP server for Scout Monitoring data interactions.
-
Monitoring AIops
— last commit 2026-08-03, shares monitoring
Governed SolarWinds Orion + PRTG + Zabbix ops: SWQL, alert rollup, health, 42 tools.
These share tags the maintainers applied themselves, such as incident-management, observability, on-call, monitoring. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: incident-management, mcp, mcp-server, model-context-protocol, monitoring, observability, on-call, sre, status-page, uptime-monitoring.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab