# UptyBots (slim)

> UptyBots, an MCP server by uptybots.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks

- Full: https://www.anchorterminal.com/tools/uptybots-monitoring.md (~1,250 tokens) · this version ~1,180 tokens · JSON https://www.anchorterminal.com/tools/uptybots-monitoring.json · canonical https://www.anchorterminal.com/tools/uptybots-monitoring
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04

# UptyBots

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by uptybots.com (https://uptybots.com/docs/mcp)
- Category: Observability & incidents (https://www.anchorterminal.com/categories/observability.md)
- Listed because: It's published in the registry under uptybots.com, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks

## Facts

- MCP registry: `com.uptybots/monitoring` 1.4.1
- Endpoint: https://mcp.uptybots.com/mcp (streamable HTTP)
- Package: npm `uptybots-mcp-server` (stdio)
- Website: https://uptybots.com/docs/mcp
- npm downloads a week: 67
- Registry entry updated: 2026-08-21

## Tools

- Tools it lists (15, about 5,335 tokens of context, `tools/list` without credentials over MCP 2026-07-28, checked 2026-10-04 22:24 UTC):
  - `list_monitors` (read-only): 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…
  - `get_monitor` (read-only): 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…
  - `create_http_monitor` (writes): 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…
  - `create_api_monitor` (writes): 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…
  - `create_ping_monitor` (writes): 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…
  - `create_port_monitor` (writes): 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…
  - `create_ssl_monitor` (writes): 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…
  - `create_domain_monitor` (writes): 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…
  - `pause_monitor` (writes): 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` (writes): 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…
  - `delete_monitor` (writes): 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.…
  - `get_incidents` (read-only): 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…
  - `get_stats_hourly` (read-only): 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…
  - `get_stats_daily` (read-only): 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…
  - `get_notifications` (read-only): 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…
- How its tools read to an agent (0 errors, 0 warnings, 0 notes, about 5,335 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):

- JSON: https://www.anchorterminal.com/api/v1/tools/uptybots-monitoring.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming