Skip to content

Monitor Hub status

Answered our latest tool-list check 9 hours ago with 25 tools. It will be marked verified after 3 successful checks in 7 days.

Answered (30 days)
2 of 2 checks
Last seen working
17 Nov, 00:17 UTC
Last commit
—
Licence
Not stated

Live checks

We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.

  • Answered
  • Needs sign-in
  • No answer
Checked (UTC)ResultResponse timeTools
17 Nov, 00:17Answered1.3 s25
16 Nov, 00:16Answered1.4 s25

Tools (25)

Read from the server on 17 Nov 2026.

list_monitors
Lists all HTTP, TCP, Ping, and Keyword monitors for the user along with current status and uptime stats.
get_monitor_details
Retrieves full diagnostic configuration, headers, assertion settings, and last check time for a specific monitor.
read_monitor_status
Provides a high-level health overview (total count, up count, down count, warning count, overall uptime percentage, average response time).
read_server_status
Lists connected physical/virtual server agents, hostnames, OS types, public/private IPs, and dynamic heartbeat status (up, down, pending).
get_server_metrics
Fetches historical CPU %, RAM %, Disk %, and Network telemetry metrics for a server agent over a specified time window.
read_incidents
Retrieves active and recent outage incidents including start time, resolution time, and AI-generated root cause analysis.
read_uptime_statistics
Calculates 24-hour uptime SLA percentages and average latency statistics across all monitors.
read_alerts
Fetches recent alert log entries and delivery notifications across email, Slack, Discord, and Telegram channels.
list_status_pages
Lists user public status page configurations and public URLs.
search_monitors
Searches monitors by target URL, keyword, or name.
list_recent_outages
Summarizes downtime events over a specified number of days along with outage duration in minutes and root cause explanations.
list_notification_channels
Lists configured alert webhooks (Slack, Discord, Telegram, Email) and alert trigger settings with sensitive tokens redacted.
create_monitor
Creates a new monitor inside Monitor Hub. Supports: • HTTP • HTTPS • API • Ping • TCP Port • Keyword Monitoring Use this tool whenever a user wants to monitor a website, API, server, endpoint, IP address or service. Returns the newly created monitor and its initial monitoring status.
update_monitor
Updates configuration for an existing monitor (name, target URL, interval, HTTP method, headers, expected status code). Use this tool when a user wants to edit or reconfigure a monitor.
pause_monitor
Pauses uptime checking for a specified monitor ID. Use this tool when a user explicitly requests to stop monitoring a website temporarily (e.g. during maintenance).
resume_monitor
Resumes active uptime monitoring for a paused monitor ID. Use this tool when a user explicitly requests to resume monitoring a website or API.
delete_monitor
Permanently removes monitoring and deletes its historical metrics. Use only when the user explicitly requests the deletion of a monitor, as this action is irreversible and deletes all associated monitoring history and data.
test_endpoint
Runs an instant live HTTP/ping probe test against any website or API URL. Measures exact response time (latency), HTTP status code, response headers, and response snippet without creating a monitor. Use this tool to verify endpoint reachability, test latency, check SSL/TLS responses, or diagnose an ongoing outage.
resolve_server_warning
Resolves an active warning sign on a monitored server agent. Closes open warning incidents for the server, restores the agent status to "up" (operational), and clears firing threshold alarms. Use this tool when you have diagnosed high CPU, RAM, or disk warnings and resolved the underlying server load.
get_incident_details
Returns incident timeline, outage duration, recovery time, failure reason, affected monitor, and timestamps. Useful when Claude needs to investigate the root cause of an outage or read historical logs for a specific downtime event.
acknowledge_incident
Marks an open incident as acknowledged and attaches an AI diagnostic note. Use this tool when you have reviewed an active incident and want to let the team know it is being investigated. Note: This tool does not resolve the incident, it only acknowledges it.
resolve_incident
Marks an ongoing incident as resolved and updates root cause analysis details. Use this tool when you have diagnosed an incident and want to close it, specifying what steps were taken to fix the issue.
trigger_test_alert
Triggers a synthetic test alert to verify notification channels (email, webhooks, Slack, Discord). Use this tool when a user wants to test if their alerting setup is working correctly.
update_status_page
Updates public status page configuration and slug for the user workspace. Use this tool when a user wants to rename or update their public status page URL.
get_monitor_history
Returns historical uptime events, incidents, and outages for a specific monitor ID. Useful for checking the long-term reliability of a specific website or server over time.