Uptime.com :): MCP server, CLI and agent surfaces
Sign-in required, tools not seen, not counted. No source names an endpoint for Uptime.com :); the connector's guess at mcp.uptime.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.
Fact sheet
| Company | Uptime.com :) |
|---|---|
| Domain | uptime.com |
| Category | Infrastructure (Ora leaderboard category) |
| MCP server | Sign-in required (OAuth without client registration) |
| Ora score | 59, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for uptime.com, a vendor-published score) |
| Company found through | Ora's public leaderboard |
| Last verified | 4 November 2026 |
MCP server
| Endpoint | https://mcp.uptime.com/mcp |
|---|---|
| How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified |
| Transport | streamable-http |
| HTTP status | 401 |
| Connected | 4 November 2026, 20:05 UTC |
| Handshake time | 1,839 ms over 1 attempt |
The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.
Connector log
2 connections on 4 November 2026, read-only methods only
- 20:00:09Z https://mcp.uptime.com/mcp sent initialize result auth-required (HTTP 401) 2032 ms
- 20:05:02Z https://mcp.uptime.com/mcp sent initialize result auth-required (HTTP 401) 1839 ms
Authentication
| Auth type | OAuth without client registration |
|---|---|
| What the challenge said | Bearer |
| Protected resource metadata | mcp.uptime.com |
| Authorization server metadata | uptime.com |
The sign-in route, step by step
- Request
https://mcp.uptime.com/mcpwithout a token. It answers 401 and aWWW-Authenticateheader. - Read the OAuth metadata at
https://uptime.com/.well-known/oauth-authorization-server. It lists no registration endpoint. - Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one.
- Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for Uptime.com :). The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.
Other agent surfaces
| Surface | Result |
|---|---|
| OpenAPI file | No OpenAPI file at the root paths checked. |
| WebMCP in the initial HTML | Not detected on the home page by the shared crawl. |
| MCP discovery file | Not found (the crawl got a non-200 answer). |
| A2A agent card | Not found (the crawl got a non-200 answer). |
| A2A agent card (older path) | Not found (the crawl got a non-200 answer). |
| agents.json | Not found (the crawl got a non-200 answer). |
| OAuth authorization server metadata | Found: uptime.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
| Registry | Listed |
|---|---|
| Official MCP Registry | No |
| GitHub MCP Registry | No |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |