Monitor Hub
com.monitorhubs/monitorhubVersion 1.0.1All-in-one monitoring for uptime, servers, incidents & status pages. Manage it all from AI chat.
Status
Responds397 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:06 UTC
- Latency
- 397 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.monitorhubs.com/mcpResponds397 msNo sign-in
Claude Code
claude mcp add --transport http monitorhub https://mcp.monitorhubs.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: monitorhub
Remote MCP server URL: https://mcp.monitorhubs.com/mcpCursor
{
"mcpServers": {
"monitorhub": {
"url": "https://mcp.monitorhubs.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"monitorhub","type":"http","url":"https://mcp.monitorhubs.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
25 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
acknowledge_incidentMarks 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. | No | No | Not declared | No |
create_monitorCreates 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. | No | No | Not declared | No |
delete_monitorPermanently 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. | Yes | No | Not declared | No |
get_incident_detailsReturns 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. | No | Yes | Not declared | No |
get_monitor_detailsRetrieves full diagnostic configuration, headers, assertion settings, and last check time for a specific monitor. | No | Yes | Not declared | No |
get_monitor_historyReturns 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. | No | Yes | Not declared | No |
get_server_metricsFetches historical CPU %, RAM %, Disk %, and Network telemetry metrics for a server agent over a specified time window. | No | Yes | Not declared | No |
list_monitorsLists all HTTP, TCP, Ping, and Keyword monitors for the user along with current status and uptime stats. | No | Yes | Not declared | No |
list_notification_channelsLists configured alert webhooks (Slack, Discord, Telegram, Email) and alert trigger settings with sensitive tokens redacted. | No | Yes | Not declared | No |
list_recent_outagesSummarizes downtime events over a specified number of days along with outage duration in minutes and root cause explanations. | No | Yes | Not declared | No |
list_status_pagesLists user public status page configurations and public URLs. | No | Yes | Not declared | No |
pause_monitorPauses 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). | No | No | Not declared | No |
read_alertsFetches recent alert log entries and delivery notifications across email, Slack, Discord, and Telegram channels. | No | Yes | Not declared | No |
read_incidentsRetrieves active and recent outage incidents including start time, resolution time, and AI-generated root cause analysis. | No | Yes | Not declared | No |
read_monitor_statusProvides a high-level health overview (total count, up count, down count, warning count, overall uptime percentage, average response time). | No | Yes | Not declared | No |
read_server_statusLists connected physical/virtual server agents, hostnames, OS types, public/private IPs, and dynamic heartbeat status (up, down, pending). | No | Yes | Not declared | No |
read_uptime_statisticsCalculates 24-hour uptime SLA percentages and average latency statistics across all monitors. | No | Yes | Not declared | No |
resolve_incidentMarks 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. | No | No | Not declared | No |
resolve_server_warningResolves 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. | No | No | Not declared | No |
resume_monitorResumes active uptime monitoring for a paused monitor ID.
Use this tool when a user explicitly requests to resume monitoring a website or API. | No | No | Not declared | No |
search_monitorsSearches monitors by target URL, keyword, or name. | No | Yes | Not declared | No |
test_endpointRuns 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. | No | Yes | Not declared | No |
trigger_test_alertTriggers 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. | No | No | Not declared | No |
update_monitorUpdates 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. | No | No | Not declared | No |
update_status_pageUpdates 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. | No | No | Not declared | No |
Details
- Registry status
- Active
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- Repository
- Not given
- Categories (suggested)
- CommunicationData and analyticsCloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared