Connect UptyBots and your agent gets 15 tools, among them create_api_monitor, create_domain_monitor, create_http_monitor. It answers at https://mcp.uptybots.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks
Description as the publisher wrote it.
| Tool | What 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_htt Inputs: name, url, frequency, requestTimeout, isActive |
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 Inputs: name, url, isActive |
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 b Inputs: name, url, frequency, requestTimeout, isActive |
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 servi Inputs: name, url, frequency, isActive |
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 Inputs: name, url, protocol, frequency, isActive |
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 Inputs: name, url, isActive |
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 inten Inputs: id |
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 doe Inputs: monitorId, page |
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 a Inputs: id |
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 mon Inputs: channel, status, page |
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 Inputs: monitorId, dateFrom, dateTo, page |
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, Inputs: monitorId, dateFrom, dateTo, page |
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 r Inputs: type, status, page |
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 monito Inputs: id |
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 runn Inputs: id |
Every block below points at https://mcp.uptybots.com/mcp. Pick your client and copy.
claude mcp add --transport http uptybots https://mcp.uptybots.com/mcp
{
"mcpServers": {
"uptybots": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.uptybots.com/mcp"]
}
}
}{
"mcpServers": {
"uptybots": {
"url": "https://mcp.uptybots.com/mcp"
}
}
}{
"servers": {
"uptybots": {
"type": "http",
"url": "https://mcp.uptybots.com/mcp"
}
}
}{
"context_servers": {
"uptybots": {
"url": "https://mcp.uptybots.com/mcp"
}
}
}{
"mcpServers": {
"uptybots": {
"serverUrl": "https://mcp.uptybots.com/mcp"
}
}
}{
"mcpServers": {
"uptybots": {
"url": "https://mcp.uptybots.com/mcp"
}
}
}name: UptyBots
version: 0.0.1
schema: v1
mcpServers:
- name: UptyBots
type: streamable-http
url: https://mcp.uptybots.com/mcp{
"mcpServers": {
"uptybots": {
"httpUrl": "https://mcp.uptybots.com/mcp"
}
}
}{
"mcpServers": {
"uptybots": {
"type": "http",
"url": "https://mcp.uptybots.com/mcp"
}
}
}{
"mcpServers": {
"uptybots": {
"url": "https://mcp.uptybots.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.uptybots.com%2Fmcp&type=streamable_http&id=uptybots&name=UptyBots
It answered our last check on 19 October 2026 in 447 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by uptybots.com and served from mcp.uptybots.com, the vendor's own domain: https://mcp.uptybots.com/mcp.
15, as returned by the server's own tools/list on 11 September 2026: create_api_monitor, create_domain_monitor, create_http_monitor, create_ping_monitor, create_port_monitor, create_ssl_monitor, delete_monitor, get_incidents, and 7 more.
It answered our last check on 19 October 2026 in 447 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.uptybots.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.uptybots. Endpoint host: mcp.uptybots.com. ARD identifier: urn:air:com.uptybots:mcp:monitoring.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.