bots.st/uptybots
UptyBots
Create and manage uptime, API, SSL, ping, and port checks
2103 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 15
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.uptybots.com/mcp - npm
npx -y uptybots-mcp-serverReleased 21 Aug 2026, version 1.3.1Set UPTYBOTS_API_KEY
What it can do
| Tool | What it says it does |
|---|---|
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 failure would be invisible to a plain page check. For an ordinary web page, create_http_monitor is lighter and enough. |
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 perfectly right up to the day the domain expires. Distinct from create_ssl_monitor, which watches the certificate rather than the… |
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 anything a browser would open. Choose create_api_monitor instead when the response body matters as well as the status code. Checks run from… |
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 anything with no web service on top. It says nothing about whether a site or service on that host is working - a box can ping perfectly… |
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 anything else that speaks its own protocol rather than HTTP - Minecraft, Rust, CS2, FiveM, Postgres, Redis, SMTP. The port must be given as… |
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 reachable - pair it with create_http_monitor when you want both. Note that such a monitor carries two independent states, one for… |
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. Confirm with the user before calling it, and prefer pause_monitor whenever the intent is only to stop the checking for a while. |
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, and which probe saw it. This is the tool for "what happened" and "how often does this break". For the shape of response times around an… |
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 protocol for PORT, certificate or registration expiry date for SSL and DOMAIN. Use it after list_monitors when the answer depends on how the… |
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 actually told about this outage" and to find a channel that is silently failing - a monitor can be detecting downtime correctly while its webhook… |
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 for comparing one monitor against another over the same window. When a single day looks wrong, zoom into it with get_stats_hourly. |
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 degrades before it fails, whether outages cluster at a particular time of day, or how long a single incident really lasted. Best over… |
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 frequency and the uptime percentage over the last 24 hours. Start here when the request names a monitor by name rather than by id, and when… |
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 the downtime does not land in the uptime figures or fire alerts. A paused monitor reports neither up nor down, so it is easy to forget one… |
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 current state is known within moments. Safe to call on a monitor that is already running. |
In its maker's words
Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks
- Website
- uptybots.com/docs/mcp
- Publisher
- uptybots.com
- Listed from
- the official MCP Registry as
com.uptybots/monitoring - Version
- 1.4.1, updated 21 Aug 2026
- Kinds of work
- Cloud and DevOps, Domains and websites, Browser and automation
The domain it lives on
- uptybots.com
- registered 12 Jun 2025 (1 year ago), at NameCheap, Inc., its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2103 ms | |
| Answered | 2218 ms | |
| Answered | 832 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.