An MCP server that connects AI assistants to your uptime monitoring

What is an MCP server?

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data. An MCP server describes what an assistant can read and which actions it can take. The PingRelay MCP server gives a connected assistant access to your monitoring account, so answers come from your real monitor data rather than general knowledge.

What an assistant can do with PingRelay

• Check health: read current monitor status and historical uptime data.
• Manage monitors: create, update, delete, pause, and resume website, API, SSL, cron job, and other monitors.
• Work incidents: manage incidents and update status pages.
• Plan maintenance: schedule maintenance windows so planned work does not trigger outage alerts.

Example prompts

• “Which of my monitors are down right now?”
• “What was the uptime of the checkout API over the last 30 days?”
• “Schedule a maintenance window for the main website tonight from 10 to 11 p.m.”
• “Pause the staging monitors while we redeploy.”
• “Add an SSL monitor for api.example.com.”

Use AI access responsibly

An assistant connected through MCP acts with the access of the account it uses. Review proposed changes before approving them, especially deletions and changes to customer-facing status pages, and use role-based access on Pro and Business to limit what each teammate can do. For automation that must run the same way every time, such as a deployment pipeline, use the PingRelay REST API instead.

Plans that include MCP access

• Pro ($29/month): MCP and REST API access, 50 monitors, 30-second checks from 10 regions, 25 status pages, and 5 teammates with role-based access.
• Business ($79/month): MCP and REST API access, 250 monitors, 30-second checks from 17 regions, 100 status pages, 15 teammates, SSO, and audit logs.

Compare every limit on the pricing page, or follow the setup steps in the PingRelay documentation.