# Monitorhubs Monitorhub MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.monitorhubs%2Fmonitorhub
Registry id: `mcp-registry/com.monitorhubs/monitorhub`
Status: live (checked 2026-11-22T16:05:15.692Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 1022
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "monitorhubs-monitorhub-mcp-server": {
      "type": "http",
      "url": "https://mcp.monitorhubs.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http monitorhubs-monitorhub-mcp-server https://mcp.monitorhubs.com/mcp
```

## Tools (25)

- `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
- `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
- `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 irrev
- `get_incident_details`: Returns incident timeline, outage duration, recovery time, failure reason, affected monitor, and timestamps. Useful when Claude needs to investigate the root ca
- `get_monitor_details`: Retrieves full diagnostic configuration, headers, assertion settings, and last check time for a specific monitor.
- `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 serve
- `get_server_metrics`: Fetches historical CPU %, RAM %, Disk %, and Network telemetry metrics for a server agent over a specified time window.
- `list_monitors`: Lists all HTTP, TCP, Ping, and Keyword monitors for the user along with current status and uptime stats.
- `list_notification_channels`: Lists configured alert webhooks (Slack, Discord, Telegram, Email) and alert trigger settings with sensitive tokens redacted.
- `list_recent_outages`: Summarizes downtime events over a specified number of days along with outage duration in minutes and root cause explanations.
- `list_status_pages`: Lists user public status page configurations and public URLs.
- `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 maintenan
- `read_alerts`: Fetches recent alert log entries and delivery notifications across email, Slack, Discord, and Telegram channels.
- `read_incidents`: Retrieves active and recent outage incidents including start time, resolution time, and AI-generated root cause analysis.
- `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).
- `read_uptime_statistics`: Calculates 24-hour uptime SLA percentages and average latency statistics across all monitors.
- `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, specifyin
- `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 
- `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.
- `search_monitors`: Searches monitors by target URL, keyword, or name.
- `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 respon
- `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 set
- `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 
- `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.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
