UptyBots MCP server

• create_api_monitorwrite actionFree

  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_monitorwrite actionFree

  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 registration; the two expire on different dates and both are worth watching.

• create_http_monitorwrite actionFree

  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 probes in several countries. Call list_monitors first so you do not create a duplicate of an existing url.

• create_ping_monitorwrite actionFree

  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 while its web server is down. Some hosting providers block ICMP, in which case the monitor will read as down.

• create_port_monitorwrite actionFree

  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 part of the url. Set protocol to UDP for game servers; most of them do not answer on TCP at all.

• create_ssl_monitorwrite actionFree

  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 reachability and one for expiry, so a certificate can be days from expiring while the check still reads up.

• delete_monitorwrite actionFree

  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_incidentsFree

  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 outage, follow up with get_stats_hourly.

• get_monitorFree

  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 check is configured, for instance whether a timeout is too tight or which port is actually being watched.

• get_notificationsFree

  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 has been rejecting every delivery. Covers the whole account, not one monitor.

• get_stats_dailyFree

  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_hourlyFree

  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 hours or days; for weeks and months use get_stats_daily instead, which returns far fewer rows.

• list_monitorsFree

  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 asked what is broken - filtering by status "down" answers that in one call. Returns an empty list rather than an error when nothing matches.

• pause_monitorFree

  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 is off.

• resume_monitorFree

  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.

• Code scan3 source files scanned25/25
• Live reliabilityremote reachable in 443ms20/20
• Tool poisoning15 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 7 write-action tools with no auth3/15
• Maintenancelast push 72 days ago12/15
• Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10

Safety score

84/100

higher than 68% of 48,255 servers

Tools

15

the typical server has 7

Tools that change things

47%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

273 ms

faster than 51% of 30,031 servers

GitHub stars

1

more than 65% of 28,688 servers

Downloads a week

76

more than 56% of 12,191 servers with a package

UptyBots: common questions

Is UptyBots MCP server safe?

Mostly: it is graded B (84/100). Read the UptyBots safety report

How do I install UptyBots?

It runs remotely at mcp.uptybots.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does UptyBots need an API key?

Yes. The registry entry asks for UPTYBOTS_API_KEY.

Is UptyBots maintained?

The last commit was 75 days ago (2026-08-21). The latest release is v1.4.1.

Is UptyBots up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of UptyBots?

Servers from other publishers that do the same job: Domain Liveness MCP server.

How does UptyBots compare with other MCP servers?

safety score 84/100 (higher than 68% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 47% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.