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
- In Hyperping, go to Project Settings, API Keys and create a
read_onlyorread_writekey. - Add the server to your MCP client (see below).
- 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
To answer "who is on call for monitor X?", chain get_monitor, get_escalation_policy, get_on_call_schedule, list_team_members.
Integrations
Rate limits
Limits apply per project, and both windows are enforced.
Open the session once and reuse it rather than calling initialize per request. Exceeding a limit returns a JSON-RPC error with a retry_after_seconds hint.
Machine-readable spec
For a dense, agent-friendly spec covering tools, query patterns and response shapes, point your client at hyperping.com/mcp/llms.txt.
Support
Open an issue here, or reach the team through hyperping.com/contact/sales.
License
MIT for the contents of this repository. Use of the hosted service is governed by the Hyperping terms and privacy policy.