UptyBots by uptybots.com
MCP server · Observability & incidents · indexed, not reviewed
HostedLocalvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks
Facts
- MCP registry
com.uptybots/monitoring· 1.4.1- Endpoint
https://mcp.uptybots.com/mcp- Packages
npmuptybots-mcp-server stdio- Website
- uptybots.com/docs/mcp
- npm / week
- 67
- Registry entry
- updated 21 Aug 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under uptybots.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 15 · about 5,335 tokens of context · checked 43 minutes ago
| Tool | What it does | Hint |
|---|---|---|
list_monitorsList 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.… | read-only |
get_monitorGet one 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… | read-only |
create_http_monitorCreate 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… | writes |
create_api_monitorCreate 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… | writes |
create_ping_monitorCreate 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… | writes |
create_port_monitorCreate 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 -… | writes |
create_ssl_monitorCreate SSL certificate 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… | writes |
create_domain_monitorCreate domain expiry 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… | writes |
pause_monitorPause 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… | writes |
resume_monitorResume 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… | writes |
delete_monitorDelete 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… | writes |
get_incidentsGet 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… | read-only |
get_stats_hourlyGet hourly statistics | 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… | read-only |
get_stats_dailyGet daily statistics | 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… | read-only |
get_notificationsGet notification history | 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… | read-only |
What https://mcp.uptybots.com/mcp answered to tools/list, asked without credentials over MCP 2026-07-28. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 0 warnings · 0 notes
Nothing to flag: every tool reads cleanly to an agent.
The checks from /check and anchor check, run each day on the list above: about 5,335 tokens of definitions. Not part of the score yet. Check your own server.