PINGZEN UPTIME MONITORING TOOLS

44 tools from the PingZen Uptime Monitoring MCP Server, categorised by risk level.

View the PingZen Uptime Monitoring policy →

READ TOOLS

15
get_check_history Get historical check results for a monitor. Returns list of checks with timestamp, status, response time, and errors. Common use cases: - 'Show me... get_current_user Get profile information for the currently authenticated user. Returns: user_id, email, plan, limits (monitors, alerts, workspaces), created_at, la... get_heartbeat Get detailed information about a specific heartbeat monitor. Returns: name, slug, status, interval, grace period, last ping, total pings, consecut... get_incident Get incident details including timeline of status updates. get_monitor_status Get real-time status of a specific monitor. Returns current status, last check time, response time, and error message if any. Common use cases: - ... get_uptime_stats Get uptime statistics for a monitor over a time period. Returns uptime percentage, total checks, failed checks, and average response time. Common ... list_alerts List all alert configurations. Returns alert name, channel, target, triggers, and active status. list_heartbeats List all heartbeat monitors for cron job / scheduled task monitoring. Heartbeats work in reverse: your service pings PingZen to confirm it ran. Re... list_incidents List incidents. Filter by status (investigating, identified, monitoring, resolved). list_monitor_groups List all monitor groups. Returns group name, monitor count, status, and health percentage. list_monitors List all monitors for a user or workspace. Returns monitor name, current status (up/down/degraded), URL, and uptime percentage. Common use cases: ... list_status_pages List all status pages in the workspace. list_telegram_groups List Telegram groups linked to the current user. Groups can receive alert notifications via the Telegram channel. Returns: Array of groups with id... list_workspaces List all workspaces for the current user. test_alert Send a test notification for an alert to verify channel configuration.

WRITE TOOLS

22
add_status_page_monitor Add a monitor to a status page. 2/5 create_alert Create a new alert rule. Sends notifications via the chosen channel when triggers fire. 2/5 create_heartbeat Create a new heartbeat monitor for cron jobs or scheduled tasks. Your service pings PingZen at the expected interval; if a ping is missed, an alert... 2/5 create_monitor Create a new uptime monitor. Supports 22 protocols (HTTP, HTTPS, TCP, DNS, SSL, etc.). Common use cases: - 'Monitor https://api.example.com every ... 3/5 create_monitor_group Create a monitor group for organizing related monitors. Returns: group_id, name, monitor_count. 2/5 create_status_page Create a new public status page with a unique slug. 2/5 create_workspace Create a new workspace for organizing monitors. Returns: workspace_id, name, color, is_default. 2/5 generate_api_key Generate a permanent API key for MCP access. API keys never expire and replace JWT tokens for long-term use. The key is shown ONCE and cannot be r... 2/5 link_telegram_group Generate a deep link URL for adding the PingZen bot to a Telegram group. Open the URL in Telegram to select a group. The link expires in 1 hour. A... 2/5 login Log in to an existing PingZen account. Returns access token, refresh token, and a permanent API key. After login, all other tools become available... 3/5 pause_heartbeat Pause a heartbeat monitor. No alerts will be sent while paused. Use resume_heartbeat to reactivate. 2/5 ping Health check endpoint for MCP server. Returns server status and version information. Use this to verify the MCP server is running and accessible. 2/5 refresh_token Refresh an expired access token using a refresh token. Returns a new access token and refresh token pair. Use this when the access token has expir... 2/5 register Create a new PingZen account. Returns access token, refresh token, and a permanent API key. A default workspace and demo monitor are automatically... 3/5 resolve_incident Resolve an incident. Shortcut for update_incident with status=resolved. 2/5 resume_heartbeat Resume a paused heartbeat monitor. Status resets to 'pending' until the next ping is received. 2/5 update_alert Update an existing alert rule. Only provided fields are changed. 2/5 update_incident Add a status update to an incident. Optionally change status (investigating -> identified -> monitoring -> resolved). 2/5 update_monitor Update an existing monitor's settings. Only provided fields are changed; others keep current values. Common use cases: - 'Rename monitor 42 to Pro... 2/5 update_monitor_group Update a monitor group. Only provided fields are changed. To replace monitors, pass the full list of monitor_ids. 2/5 update_status_page Update a status page's title, slug, description, theme, or visibility. 2/5 update_workspace Update a workspace's name, description, or color. Only provided fields are changed. 2/5

DESTRUCTIVE TOOLS

6

EXECUTE TOOLS

1
How many tools does the PingZen Uptime Monitoring MCP server have? +

The PingZen Uptime Monitoring MCP server exposes 44 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on PingZen Uptime Monitoring tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the PingZen Uptime Monitoring server.

What risk categories do PingZen Uptime Monitoring tools fall into? +

PingZen Uptime Monitoring tools are categorised as Read (15), Write (22), Destructive (6), Execute (1). Each category has a recommended default policy.

Enforce policies on PingZen Uptime Monitoring

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.