Hyperping vs Pagerduty MCP
A side-by-side look at the Hyperping and Pagerduty MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hyperping for monitoring work over a hosted endpoint; choose Pagerduty MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hyperping when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_monitors, get_monitor, search_monitors_by_name.
Choose Pagerduty MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PAGERDUTY_USER_API_KEY. - You want tools like
create_alert_grouping_setting, delete_alert_grouping_setting, get_alert_grouping_setting.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 51/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | PAGERDUTY_USER_API_KEY |
| Verified owner |
Tools & capabilities
Hyperping tools 26
list_monitorsPaginated monitors, filterable by `up`, `down`, `paused`, `ssl_expiring`.get_monitorOne monitor by UUID.search_monitors_by_nameCase-insensitive substring search over names and URLs.create_monitorCreate an HTTP, ICMP, port or DNS monitor.update_monitorPatch a monitor. Unspecified fields are preserved.pause_monitorStop checks and alerts for a monitor.resume_monitorResume a paused monitor.get_status_summaryUp, down and paused counts, plus what is currently down and since when.list_outagesPaginated outages, filterable by status, type or search term.get_outageOne outage, with acknowledgements, description and root cause.get_outage_timelineDetection, cross-region verification, alert dispatch, acknowledgement, resolution.get_monitor_outagesOutages scoped to a single monitor.- +14 more on the listing page
Pagerduty MCP tools 80
create_alert_grouping_settingCreates a new alert grouping settingdelete_alert_grouping_settingDeletes an alert grouping settingget_alert_grouping_setting
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Hyperping
{
"mcpServers": {
"hyperping": {
"url": "https://api.hyperping.io/v1/mcp"
}
}
}
Pagerduty MCP
{
"mcpServers": {
"pagerduty-mcp": {
"command": "uvx",
"args": [
"pagerduty-mcp"
],
"env": {
"PAGERDUTY_USER_API_KEY": "YOUR_PAGERDUTY_USER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Hyperping is categorized under Monitoring and uses a remote HTTP/SSE transport. Pagerduty MCP belongs to Monitoring and uses a local stdio subprocess. Pick Hyperping for monitoring work and Pagerduty MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Hyperping has no declared pricing — check the project's own site. Pagerduty MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hyperping and pagerduty-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hyperping has a quality signal of 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Pagerduty MCP has 40/100 (Fair) with 2 views, 0 installs and 79 GitHub stars.