com.uptybots/monitoring

up checked 2026-11-11T10:38:23.742Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

UptyBots

Publisher-provided description

Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks

Summary by lookupd

Creates, pauses, resumes and deletes uptime monitors for HTTP, API, SSL, ping, port and domain checks, and reads incidents, stats and…

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http monitoring https://mcp.uptybots.com/mcp

Claude Code, npm package (stdio)

claude mcp add monitoring -- npx -y uptybots-mcp-server

Codex, remote (streamable-http)

codex mcp add monitoring --url https://mcp.uptybots.com/mcp

Codex, npm package (stdio)

codex mcp add monitoring -- npx -y uptybots-mcp-server

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "monitoring": {
      "url": "https://mcp.uptybots.com/mcp"
    }
  }
}

Cursor, npm package (stdio) → .cursor/mcp.json

{
  "mcpServers": {
    "monitoring": {
      "command": "npx",
      "args": [
        "-y",
        "uptybots-mcp-server"
      ]
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (15 tools)

Publisher-provided text

• 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 f
• 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 protoco
• 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 anyt
• 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 failur
• 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 an
• 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 an
• 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
• 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 pe
• 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
• 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 curre
• 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. Conf
• 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,
• 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
• 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 f
• 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 actuall

Details

• Version: 1.4.1
• Transports: streamable-http, stdio
• Uptime (7 days): 100%
• Median latency: 377 ms
• First indexed: 2026-11-01T08:59:44.859Z
• Last seen in registry: 2026-11-01T08:59:44.909Z
• Website: https://uptybots.com/docs/mcp

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/com.uptybots/monitoring.svg)](https://lookupd.com/servers/com.uptybots/monitoring)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp