DevOps
uptybots.com
Provides uptime monitoring for websites, APIs, SSL, domains, and ports, integrating with AI assistants via MCP.
ENDPOINT 1
https://mcp.uptybots.com/mcp
MCP server metadata
- Name
- uptybots
- Version
- 1.4.1
Known tools 15
get_monitorRead 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.
Inferred read-onlycreate_http_monitorWatch a web page or endpoint over HTTP/HTTPS and treat an unexpected status code, a timeout or a connection failure as downtime.
Inferred read-onlycreate_api_monitorWatch a JSON or REST endpoint where the response itself matters, not only that the host answered.
Inferred read-onlycreate_ping_monitorWatch a host with ICMP ping: it answers whether the machine is reachable at all, and reports round-trip time and packet loss.
Inferred read-onlycreate_port_monitorWatch one TCP or UDP port on a host and report it up only when the service behind it actually answers.
Inferred read-onlycreate_ssl_monitorWatch a TLS certificate: whether it is valid, who issued it, and how many days remain before it expires.
Inferred read-onlycreate_domain_monitorWatch a domain registration and report how long is left before it lapses, read from WHOIS.
Inferred read-onlyresume_monitorStart checking a paused monitor again, with the configuration it had before.
Inferred read-onlydelete_monitorPermanently delete a monitor together with its entire check history, incidents and statistics.
Potential side effectsget_incidentsRead 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.
Inferred read-onlyget_stats_hourlyResponse time and uptime for one monitor broken down by hour, with min, max, average and p95 per bucket.
Inferred read-onlyget_stats_dailyResponse time and uptime for one monitor aggregated per day, with min, max, average and p95.
Inferred read-onlyget_notificationsRead the alerts this account has sent, across email, Telegram, webhook and the web interface, with the delivery outcome of each.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.uptybots]
url = "https://mcp.uptybots.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"uptybots": {
"type": "http",
"url": "https://mcp.uptybots.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: uptybots
Remote MCP URL: https://mcp.uptybots.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"uptybots": {
"url": "https://mcp.uptybots.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"uptybots": {
"type": "http",
"url": "https://mcp.uptybots.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "uptybots",
"transport": "streamable-http",
"url": "https://mcp.uptybots.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.