Developer · Remote MCP server
uptimemonitoring.com
Agent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.uptimemonitoring/mcp- Version
- 1.0.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-20
- Updated
- 2026-06-20
- Publisher
- com.uptimemonitoring
- Namespace
- Namespace verified by the MCP Registry via the domain uptimemonitoring.com · how
- Website
- uptimemonitoring.com/docs/mcp/
- Repository
- github.com/uptimemonitoring/examples
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.uptimemonitoring.com/mcp | Authorization (required, secret) |
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 uptimemonitoring.com
uptimemonitoring.com is a remote MCP server: there is nothing to install. Its endpoint is https://api.uptimemonitoring.com/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.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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 |
|---|---|
| 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 |
| UptimelyUptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry. | 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 |
| URL to Clean Markdown for LLMs & RAGFetch URLs and return clean Markdown for RAG - nav, ads and boilerplate stripped. | Remote · HTTPLive check: sign-in required |