Developer · Remote MCP server
Uptimely
Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.getuptimely/uptimely- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-10
- Updated
- 2026-09-10
- Publisher
- com.getuptimely
- Namespace
- Namespace verified by the MCP Registry via the domain getuptimely.com · how
- Website
- getuptimely.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.getuptimely.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Uptimely
Uptimely is a remote MCP server: there is nothing to install. Its endpoint is https://app.getuptimely.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| uploads.shHost files from coding agents; stage on a branch and attach to GitHub PRs. | Remote & Local · HTTP, stdioLive check: sign-in required |
| UpshiftAudit a site's structured data and llms.txt, match a trade to a template, and quote real prices. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| upstash MCP-SERVERManage Upstash databases and resources through the Upstash Developer API. | Local · stdio |
| Uptimebolt MCP ServerAI-powered infrastructure monitoring - health, incidents, predictions, RCA, deploy safety. | Local · stdio |
| uptimemonitoring.comAgent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier. | Remote · HTTPLive check: sign-in required |
| Uptimerobot MCPUptime, port, TLS and DNS checks for any site - no API key. | Local · stdio |
| UpToCodeEvidence-backed architecture-quality analysis for Python agent applications. | Remote & Local · HTTP, stdioLive check: sign-in required |
| UptyBotsUptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks. | Remote & Local · HTTP, stdioLive check: ✓ handshake |