Reviews
No review yet. Used UptyBots? Be the first to help others choose.What it does
UptyBots is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 10h ago (live check)Hosted endpoint
https://mcp.uptybots.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http uptybots https://mcp.uptybots.com/mcp
Install package
- NPM
uptybots-mcp-serverv1.3.1 · runs locally (stdio)
Required: UPTYBOTS_API_KEY (get it from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"uptybots": {
"url": "https://mcp.uptybots.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 10h agoONLINE UptyBots answered an MCP connection on 17 Nov 2026 and introduced itself as uptybots 1.4.1 (MCP protocol 2025-06-18).
15 tools offered to AI assistants
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 rget_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 acreate_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 bcreate_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_httcreate_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 servicreate_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, CS2create_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 suchcreate_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_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 alerts. A paused monitoresume_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 runndelete_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 intenget_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
Show 3 more
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,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 dayget_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
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | uptybots-mcp-server | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://mcp.uptybots.com/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Package registries | npm | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://uptybots.com/docs/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.4.1 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is UptyBots still online?
Free alerts · no account▲ 0Do you run UptyBots? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about UptyBots
How do I connect UptyBots?
Use the hosted endpoint https://mcp.uptybots.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does UptyBots need an API key or token?
Yes. The registry entry lists a required value: UPTYBOTS_API_KEY. Get it from the publisher.
What tools does UptyBots offer?
When Electra Index connected on 17 Nov 2026, it listed 15 tools: list_monitors, get_monitor, create_http_monitor, create_api_monitor, create_ping_monitor, create_port_monitor, create_ssl_monitor, create_domain_monitor and more. The full list is in "Live check" above.
Is UptyBots online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 10h ago.