Skip to content
MCP server

Monitor Hub

Query uptime, server telemetry and incidents, and manage monitors, from an AI chat

Status and history

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

Pricing
Freemium
Platforms
Web, API, Linux
Runs
Remotely
Version
1.0.1
Listing updated
3 days ago

About Monitor Hub

Monitor Hub is a freemium MCP server for cloud and infrastructure. It runs as a hosted remote server, so there is nothing to install locally.

Monitor Hub is a hosted monitoring platform for websites, APIs, Windows and Linux servers, SSL certificates and domains, and this connector lets Claude, Cursor, ChatGPT, Gemini, Windsurf and VS Code agents work with it. Authorisation uses OAuth 2.1 with PKCE and dynamic client registration, so no raw API secret needs copying.

Tokens carry one of two scopes: mcp:read for query-only telemetry, and mcp:write for creating monitors and resolving server warnings. Every AI query is written to a workspace audit log with timestamp, tool name, IP address and latency. Example requests on the site include creating an API monitor, checking server CPU load and resolving warnings.

Behind it, checks run from several edge locations with a 3% hysteresis deadband to avoid false alarms, and the platform covers JSONPath assertions on API responses, WHOIS expiry tracking, a lightweight open-source server agent and white-label status pages. Plans are Free, Starter, Pro and Business, with the AI platform and number of access keys rising by tier.

Install

Run in a terminal

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

Add to Settings → Connectors → Add custom connector

https://mcp.monitorhubs.com/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "monitorhub": {
      "url": "https://mcp.monitorhubs.com/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "monitorhub": {
      "type": "http",
      "url": "https://mcp.monitorhubs.com/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "monitorhub": {
      "serverUrl": "https://mcp.monitorhubs.com/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

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

Tools this server provides (25)

Read directly from the server.

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.

What it does

OAuth with scopes
Separates read-only telemetry from monitor management.
Audit trail
Logs each AI query with tool, time, IP and latency.
Uptime and API checks
Covers websites and APIs, including JSONPath assertions.
Server telemetry
Reports CPU, memory, disks and processes from a local agent.
Incident root cause
Correlates CPU, memory and disk pressure with diagnostics.
Status pages
Offers white-label public or password-protected pages.

Good for

  • Ask an assistant whether a site is up and how slow it is
  • Create an API monitor from a chat prompt
  • Check CPU load on a Linux server
  • Review incident causes after an outage
  • Resolve server warnings without opening the dashboard

Pricing

Freemium

Free plan; Starter, Pro and Business tiers (prices not shown)

Prices change. Check monitorhubs.com before you buy.

Monitor Hub FAQ

How does sign-in work?

OAuth 2.1 with PKCE; you pick your AI client in Monitor Hub settings and approve the scopes.

Can the assistant change things?

Only with the mcp:write scope. mcp:read is query-only.

Is there a free plan?

Yes. The site says you can start free without a credit card.

Which clients are supported?

Claude, Cursor, ChatGPT, Gemini, Windsurf, and VS Code with Continue.

Is Monitor Hub free?

Monitor Hub has a free plan, with paid plans for more usage or features.

How do I add Monitor Hub to Claude Code?

Run this command in your terminal: claude mcp add --transport http monitorhub https://mcp.monitorhubs.com/mcp

What are the best alternatives to Monitor Hub?

The closest alternatives to Monitor Hub are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to Monitor Hub

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools