Developer · Remote MCP server
UptyBots
Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.uptybots/monitoring- Version
- 1.4.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-21
- Updated
- 2026-08-21
- Publisher
- com.uptybots
- Namespace
- Namespace verified by the MCP Registry via the domain uptybots.com · how
- Website
- uptybots.com/docs/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.uptybots.com/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 200)
- Handshake
- uptybots 1.4.1 · protocol 2025-06-18
- Tools discovered
15 - show names
list_monitors,get_monitor,create_http_monitor,create_api_monitor,create_ping_monitor,create_port_monitor,create_ssl_monitor,create_domain_monitor,pause_monitor,resume_monitor,delete_monitor,get_incidents,get_stats_hourly,get_stats_daily,get_notifications- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | uptybots-mcp-server | 1.3.1 | stdio |
How to connect UptyBots
UptyBots is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.uptybots.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.
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.
It can also run locally from a Node.js package published to the npm registry: uptybots-mcp-server version 1.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y uptybots-mcp-server@1.3.1. It reads these environment variables: UPTYBOTS_API_KEY (required, secret) and UPTYBOTS_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"monitoring": {
"command": "npx",
"args": [
"-y",
"uptybots-mcp-server@1.3.1"
],
"env": {
"UPTYBOTS_API_KEY": "<secret>",
"UPTYBOTS_API_URL": "<value>"
}
}
}
}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 |
|---|---|
| UptimelyUptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry. | Remote · HTTPLive check: sign-in required |
| 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 |
| 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 |
| UrlhausURLhaus MCP - wraps abuse.ch URLhaus malware URL database (free, no auth) | Remote · HTTPLive check: ✓ handshake |
| URLpipeRead any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse. | Remote · HTTPLive check: ✓ handshake |
| URLs-LEExtract URLs from documentation, configuration and code, with their protocol and position. | Local · stdio |