MCP server for UptyBots — connect AI assistants to your uptime monitors
MCP server for UptyBots — connect AI assistants to your uptime monitors
active Production-safe Score 92/100 http no auth
At a glance
| Endpoint | https://mcp.uptybots.com/mcp |
|---|---|
| Source | https://github.com/uptybots/mcp-server |
| Transport | http |
| Tools | 15 |
| Auth | none |
| First seen | 2026-08-18 18:44:53 |
| Last checked | 2026-11-17 21:45:26 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 570 / 781 ms |
| Last successful check | 2026-11-17 21:45:26 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (15)
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, curget_monitor— Read one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HTcreate_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 thecreate_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 andcreate_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 sercreate_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, dacreate_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, notcreate_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:pause_monitor— Stop checking a monitor without deleting it. History and configuration survive, and resume_monitor puts it back to work. Use this around plaresume_monitor— Start checking a paused monitor again, with the configuration it had before. The first check runs immediately rather than after the usual indelete_monitor— Permanently delete a monitor together with its entire check history, incidents and statistics. This cannot be undone and there is no trash tget_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 - HTTPget_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 probleget_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 weget_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 a
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:45:26 | ✓ | ✓ | 492 ms | 90 | active |
| 2026-11-17 21:30:21 | ✓ | ✓ | 654 ms | 90 | active |
| 2026-11-17 21:15:00 | ✓ | ✓ | 517 ms | 90 | active |
| 2026-11-17 20:59:44 | ✓ | ✓ | 604 ms | 90 | active |
| 2026-11-17 20:44:43 | ✓ | ✓ | 818 ms | 90 | active |
| 2026-11-17 20:29:42 | ✓ | ✓ | 591 ms | 90 | active |
| 2026-11-17 20:14:37 | ✓ | ✓ | 885 ms | 90 | active |
| 2026-11-17 19:58:39 | ✓ | ✓ | 511 ms | 90 | active |
| 2026-11-17 19:43:38 | ✓ | ✓ | 476 ms | 90 | active |
| 2026-11-17 19:28:36 | ✓ | ✓ | 474 ms | 90 | active |
| 2026-11-17 19:13:32 | ✓ | ✓ | 661 ms | 90 | active |
| 2026-11-17 18:56:04 | ✓ | ✓ | 530 ms | 90 | active |
| 2026-11-17 18:40:57 | ✓ | ✓ | 518 ms | 90 | active |
| 2026-11-17 18:25:51 | ✓ | ✓ | 540 ms | 90 | active |
| 2026-11-17 18:10:35 | ✓ | ✓ | 681 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.uptybots.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-uptybots-com-mcp # JSON