# Uptybots Monitoring MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.uptybots%2Fmonitoring
Registry id: `mcp-registry/com.uptybots/monitoring`
Status: live (checked 2026-10-27T00:22:36.708Z)

## Verdict

Uptybots Monitoring MCP server answered 99.81% of Glimind's liveness checks over 30 days, better than 24% of MCP servers, with 760 ms median handshake and 14 outages in 90 days. Its agent-readiness grade is A (100/100) across 15 tools, costing an agent about 3,677 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.81% | 24% of MCP servers |
| Median handshake latency | 760 ms | 31% of MCP servers |
| p95 handshake latency | 2761 ms | — |
| Checks in 30 days | 4,933 | — |
| Outages, 90 days | 14 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 100/100 (A) | 94% of MCP servers |
| Tools | 15 | — |
| Tool-list size for an agent | ~3,677 tokens | 42% of MCP servers |
| Days observed | 29 | — |

## Install

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

Claude Code:

```sh
claude mcp add --transport http uptybots-monitoring-mcp-server https://mcp.uptybots.com/mcp
```

## Tools (15)

- `create_api_monitor`: Watch a JSON or REST endpoint where the response itself matters, not only that the host answered. Use it for health endpoints, webhooks and any API whose failur
- `create_domain_monitor`: Watch a domain registration and report how long is left before it lapses, read from WHOIS. This catches the failure no uptime check can see: everything works pe
- `create_http_monitor`: Watch a web page or endpoint over HTTP/HTTPS and treat an unexpected status code, a timeout or a connection failure as downtime. This is the right type for anyt
- `create_ping_monitor`: Watch a host with ICMP ping: it answers whether the machine is reachable at all, and reports round-trip time and packet loss. Use it for servers, routers and an
- `create_port_monitor`: Watch one TCP or UDP port on a host and report it up only when the service behind it actually answers. This is the type for game servers, databases, mail and an
- `create_ssl_monitor`: Watch a TLS certificate: whether it is valid, who issued it, and how many days remain before it expires. This is about the certificate, not about the site being
- `delete_monitor`: Permanently delete a monitor together with its entire check history, incidents and statistics. This cannot be undone and there is no trash to restore from. Conf
- `get_incidents`: Read the downtime history of one monitor: when each outage began, when it ended, how long it lasted and what the failure actually was - HTTP status, error text,
- `get_monitor`: Read one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HTTP, port and protoco
- `get_notifications`: Read the alerts this account has sent, across email, Telegram, webhook and the web interface, with the delivery outcome of each. Use it to answer "was I actuall
- `get_stats_daily`: Response time and uptime for one monitor aggregated per day, with min, max, average and p95. This is the tool for reports and trends over weeks or months, and f
- `get_stats_hourly`: Response time and uptime for one monitor broken down by hour, with min, max, average and p95 per bucket. Use it to see the shape of a problem: whether a service
- `list_monitors`: List the monitors on the account, newest first, 30 per page. Each entry carries the id needed by every other tool, plus name, url, type, current status, check f
- `pause_monitor`: Stop checking a monitor without deleting it. History and configuration survive, and resume_monitor puts it back to work. Use this around planned maintenance so 
- `resume_monitor`: Start checking a paused monitor again, with the configuration it had before. The first check runs immediately rather than after the usual interval, so the curre

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