Skip to content

Monitor Hub MCP server

com.monitorhubs/monitorhubmonitorhubs.comstreamable-httpv1.0.1Scanned

All-in-one monitoring for uptime, servers, incidents & status pages. Manage it all from AI chat.

25 tools: 1 can delete or cancel things, 10 change things and 14 only read.

Tools: 1 delete, 0 irreversible, 10 write, 14 read.
  • Reads private data · 2
  • Reads text others write · 4
  • Can send data out · 3
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Monitor Hub MCP server can do

The Monitor Hub MCP server is published by monitorhubs.com, a domain the MCP Registry verified. It has 25 tools. It can delete or cancel things (1 tool: delete_monitor) and create or change data (10 tools: create_monitor, update_monitor, pause_monitor, resume_monitor and 6 more). 14 tools only read.

2 tools read private data (read_alerts and list_notification_channels); 4 tools bring in text other people can write (list_monitors, read_alerts, search_monitors and 1 more); 3 tools can send data out of your system (create_monitor, update_monitor and test_endpoint). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

25 tools

Deletes or cancels 1Claude Code: deny
  • delete_monitorPermanently removes monitoring and deletes its historical metrics.No findings

    Why it is in this group

    • The name "delete_monitor" says "delete": a word for removing or ending something.
    • The description says "Permanently removes".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 10Claude Code: ask
  • acknowledge_incidentMarks an open incident as acknowledged and attaches an AI diagnostic note.No findings

    Why it is in this group

    • The description's first verb is "mark": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • create_monitorCreates a new monitor inside Monitor Hub.Can send data outNo findings

    Why it is in this group

    • The name "create_monitor" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • pause_monitorPauses uptime checking for a specified monitor ID.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • resolve_incidentMarks an ongoing incident as resolved and updates root cause analysis details.No findings

    Why it is in this group

    • The name "resolve_incident" says "resolve": a word for reading.
    • The description's first verb is "mark": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • resolve_server_warningResolves an active warning sign on a monitored server agent.1 finding

    Why it is in this group

    • The name "resolve_server_warning" says "resolve": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "resolve_server_warning" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "resolve_server_warning" says "resolve": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • resume_monitorResumes active uptime monitoring for a paused monitor ID.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Resumes active uptime monitoring for a paused monitor ID. Use this tool when a user explicitly requests to resume monitoring a website or API.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • test_endpointRuns an instant live HTTP/ping probe test against any website or API URL.Can send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "test_endpoint" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • trigger_test_alertTriggers a synthetic test alert to verify notification channels (email, webhooks, Slack, Discord).No findings

    Why it is in this group

    • The name "trigger_test_alert" says "trigger": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • update_monitorUpdates configuration for an existing monitor (name, target URL, interval, HTTP method, headers, expected status code).Can send data outNo findings

    Why it is in this group

    • The name "update_monitor" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • update_status_pageUpdates public status page configuration and slug for the user workspace.No findings

    Why it is in this group

    • The name "update_status_page" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 14Show 14 read-only tools
  • get_incident_detailsReturns incident timeline, outage duration, recovery time, failure reason, affected monitor, and timestamps.No findings

    Why it is in this group

    • The name "get_incident_details" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_monitor_detailsRetrieves full diagnostic configuration, headers, assertion settings, and last check time for a specific monitor.No findings

    Why it is in this group

    • The name "get_monitor_details" says "get": a word for reading.
    Description, as the server wrote it
    Retrieves full diagnostic configuration, headers, assertion settings, and last check time for a specific monitor.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_monitor_historyReturns historical uptime events, incidents, and outages for a specific monitor ID.No findings

    Why it is in this group

    • The name "get_monitor_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_server_metricsFetches historical CPU %, RAM %, Disk %, and Network telemetry metrics for a server agent over a specified time window.No findings

    Why it is in this group

    • The name "get_server_metrics" says "get": a word for reading.
    Description, as the server wrote it
    Fetches historical CPU %, RAM %, Disk %, and Network telemetry metrics for a server agent over a specified time window.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_monitorsLists all HTTP, TCP, Ping, and Keyword monitors for the user along with current status and uptime stats.Reads text others writeNo findings

    Why it is in this group

    • The name "list_monitors" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Lists all HTTP, TCP, Ping, and Keyword monitors for the user along with current status and uptime stats.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_notification_channelsLists configured alert webhooks (Slack, Discord, Telegram, Email) and alert trigger settings with sensitive tokens redacted.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_notification_channels" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Lists configured alert webhooks (Slack, Discord, Telegram, Email) and alert trigger settings with sensitive tokens redacted.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_recent_outagesSummarizes downtime events over a specified number of days along with outage duration in minutes and root cause explanations.No findings

    Why it is in this group

    • The name "list_recent_outages" says "list": a word for reading.
    Description, as the server wrote it
    Summarizes downtime events over a specified number of days along with outage duration in minutes and root cause explanations.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_status_pagesLists user public status page configurations and public URLs.No findings

    Why it is in this group

    • The name "list_status_pages" says "list": a word for reading.
    Description, as the server wrote it
    Lists user public status page configurations and public URLs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_alertsFetches recent alert log entries and delivery notifications across email, Slack, Discord, and Telegram channels.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "read_alerts" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Fetches recent alert log entries and delivery notifications across email, Slack, Discord, and Telegram channels.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_incidentsRetrieves active and recent outage incidents including start time, resolution time, and AI-generated root cause analysis.No findings

    Why it is in this group

    • The name "read_incidents" says "read": a word for reading.
    Description, as the server wrote it
    Retrieves active and recent outage incidents including start time, resolution time, and AI-generated root cause analysis.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_monitor_statusProvides a high-level health overview (total count, up count, down count, warning count, overall uptime percentage, average response time).No findings

    Why it is in this group

    • The name "read_monitor_status" says "read": a word for reading.
    Description, as the server wrote it
    Provides a high-level health overview (total count, up count, down count, warning count, overall uptime percentage, average response time).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_server_statusLists connected physical/virtual server agents, hostnames, OS types, public/private IPs, and dynamic heartbeat status (up, down, pending).No findings

    Why it is in this group

    • The name "read_server_status" says "read": a word for reading.
    Description, as the server wrote it
    Lists connected physical/virtual server agents, hostnames, OS types, public/private IPs, and dynamic heartbeat status (up, down, pending).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_uptime_statisticsCalculates 24-hour uptime SLA percentages and average latency statistics across all monitors.No findings

    Why it is in this group

    • The name "read_uptime_statistics" says "read": a word for reading.
    Description, as the server wrote it
    Calculates 24-hour uptime SLA percentages and average latency statistics across all monitors.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • search_monitorsSearches monitors by target URL, keyword, or name.Reads text others writeNo findings

    Why it is in this group

    • The name "search_monitors" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Searches monitors by target URL, keyword, or name.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__monitorhub__list_notification_channels",
      "mcp__monitorhub__read_alerts"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.monitorhubs.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.monitorhubs.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (1 destructive, 10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.monitorhubs.com/mcp: tools/list returned 25 tools to an anonymous client, including delete_monitor (destructive), create_monitor (write), update_monitor (write), pause_monitor (write), resume_monitor (write) and 6 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "test_endpoint" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "resolve_server_warning" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "resolve_server_warning" says "resolve": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__monitorhub__list_monitors",
      "mcp__monitorhub__get_monitor_details",
      "mcp__monitorhub__read_monitor_status",
      "mcp__monitorhub__read_server_status",
      "mcp__monitorhub__get_server_metrics",
      "mcp__monitorhub__read_incidents",
      "mcp__monitorhub__read_uptime_statistics",
      "mcp__monitorhub__read_alerts",
      "mcp__monitorhub__list_status_pages",
      "mcp__monitorhub__search_monitors",
      "mcp__monitorhub__list_recent_outages",
      "mcp__monitorhub__list_notification_channels",
      "mcp__monitorhub__get_incident_details",
      "mcp__monitorhub__get_monitor_history"
    ],
    "ask": [
      "mcp__monitorhub__create_monitor",
      "mcp__monitorhub__update_monitor",
      "mcp__monitorhub__pause_monitor",
      "mcp__monitorhub__resume_monitor",
      "mcp__monitorhub__test_endpoint",
      "mcp__monitorhub__resolve_server_warning",
      "mcp__monitorhub__acknowledge_incident",
      "mcp__monitorhub__resolve_incident",
      "mcp__monitorhub__trigger_test_alert",
      "mcp__monitorhub__update_status_page"
    ],
    "deny": [
      "mcp__monitorhub__delete_monitor"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as monitorhub. Review it before you use it.

Capability tags behind 7 rules
  • mcp__monitorhub__list_monitors untrusted-input
  • mcp__monitorhub__read_alerts private-data, untrusted-input
  • mcp__monitorhub__search_monitors untrusted-input
  • mcp__monitorhub__list_notification_channels private-data, untrusted-input
  • mcp__monitorhub__create_monitor outbound
  • mcp__monitorhub__update_monitor outbound
  • mcp__monitorhub__test_endpoint outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.monitorhubs/monitorhub/verify?hash=22784d241eb5ec78e87ac4146bfde8dc13e7469daacbc2851ed251ffe5a0eca9" | jq -e '.changed == false'

Pinned hash 22784d241eb5, from Nov 13, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.monitorhubs/monitorhub/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.monitorhubs/monitorhub
[![Anlyon Radar](https://radar.anlyon.com/badge/com.monitorhubs/monitorhub.svg)](https://radar.anlyon.com/servers/com.monitorhubs/monitorhub)

Source: MCP Registry. Synced Nov 13, 2026, 17:17 UTC.

Monitor Hub MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Monitor Hub MCP server safe?

No scan can promise that. What its definitions show: 25 tools, 11 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Monitor Hub MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_monitor.

Can the Monitor Hub MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Monitor Hub MCP server have?

25 tools: 1 destructive, 10 write, 14 read. delete_monitor, create_monitor, update_monitor, pause_monitor, resume_monitor, test_endpoint, resolve_server_warning, acknowledge_incident and 17 more.

Does the Monitor Hub MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Monitor Hub MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_monitor, update_monitor and test_endpoint.

Has the Monitor Hub MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.