// MCP TOOL REFERENCE

PINGZEN UPTIME MONITORING TOOLS

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

View the PingZen Uptime Monitoring policy → Token cost: 4,664 tokens →

// ALL 44 PINGZEN UPTIME MONITORING TOOLS

READ 15 tools

Read get_check_history Get historical check results for a monitor. Returns list of checks with timestamp, status, response time, a... Read get_current_user Get profile information for the currently authenticated user. Returns: user_id, email, plan, limits (monit... Read get_heartbeat Get detailed information about a specific heartbeat monitor. Returns: name, slug, status, interval, grace ... Read get_incident Get incident details including timeline of status updates. Read get_monitor_status Get real-time status of a specific monitor. Returns current status, last check time, response time, and err... Read get_uptime_stats Get uptime statistics for a monitor over a time period. Returns uptime percentage, total checks, failed che... Read list_alerts List all alert configurations. Returns alert name, channel, target, triggers, and active status. Read list_heartbeats List all heartbeat monitors for cron job / scheduled task monitoring. Heartbeats work in reverse: your serv... Read list_incidents List incidents. Filter by status (investigating, identified, monitoring, resolved). Read list_monitor_groups List all monitor groups. Returns group name, monitor count, status, and health percentage. Read list_monitors List all monitors for a user or workspace. Returns monitor name, current status (up/down/degraded), URL, an... Read list_status_pages List all status pages in the workspace. Read list_telegram_groups List Telegram groups linked to the current user. Groups can receive alert notifications via the Telegram ch... Read list_workspaces List all workspaces for the current user. Read test_alert Send a test notification for an alert to verify channel configuration.

WRITE 22 tools

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

DESTRUCTIVE 6 tools

Destructive delete_alert Delete an alert rule. Pass confirm=true to confirm deletion. Destructive delete_heartbeat Delete a heartbeat monitor and all its ping history. This action is IRREVERSIBLE. Safety: Pass confirm=tru... Destructive delete_monitor Delete a monitor and all its data (check results, alerts, incidents). This action is IRREVERSIBLE. Safety:... Destructive delete_monitor_group Delete a monitor group. Monitors are NOT deleted, only ungrouped. Pass confirm=true to confirm deletion. Destructive delete_telegram_group Unlink a Telegram group. The bot stays in the group, but alerts will no longer be sent to it. Pass confirm... Destructive remove_status_page_monitor Remove a monitor from a status page.

EXECUTE 1 tools

Execute execute_check Run an immediate health check for a monitor. Returns real-time result without waiting for the next schedule...

// FAQ

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? +

Route the PingZen Uptime Monitoring server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the 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.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.