The UptyBots MCP server,
connected in one click.

“Use “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, cur.”

“Use “get_monitor”: Read one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HT.”

“Use “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.”

“Use “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.”

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, cur

get_monitor — Read one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HT

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

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

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 ser

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, da

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

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: