FRENES

Monitoring and observability · MCP server

Uptybots MCP: MCP server, setup and security

Uptybots MCP is an open-source MCP server published on GitHub that lets an AI agent monitor websites and APIs and review incidents and uptime history. Its repository has 1 stars and its last commit is from August 21, 2026 and it is licensed under MIT.

OfficialActively maintained

What Uptybots MCP does

According to its repository: “Uptime monitoring for websites, APIs, SSL certificates, domain expiry, ping and TCP/UDP ports: manage monitors and view incidents and uptime history.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Uptybots MCP is listed under Monitoring and observability, a category of 57 servers in the directory, where it ranks #56 by stars.

Topics declared by the repository: claude, cursor, monitoring, nodejs, uptime, uptime-monitoring.

Installing and connecting Uptybots MCP

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript. Listed systems: macOS, Windows, Linux.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Uptybots MCP. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on April 4, 2026, the uptybots/mcp-server repository has 1 stars and 0 forks, with 0 open issues. It has more stars than 7% of the servers in the directory. Last change 2 months ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.

NetdataNetdata : 81.1K81.1KOpenstatusOpenstatus : 9.2K9.2KOneUptimeOneUptime : 7.8K7.8KMCP grafanaMCP grafana : 3.6K3.6KMarmot Data CatalogMarmot Data Catalog : 623623Watch skillWatch skill : 520520HomebutlerHomebutler : 305305Zabbix MCP serverZabbix MCP server : 261261Uptybots MCPUptybots MCP : 11
GitHub stars of the most followed servers in the category (log scale); Uptybots MCP in orange. Checked October 25, 2026.

Verdict

Uptybots MCP is a reasonable choice; check the points below before connecting it.

Strengths

  • Maintained by the service's own vendor
  • Active project: recent commit
  • Permissive licence (MIT)

Limitations

  • Few visible users
  • Install from source

Frequently asked questions

How do I install Uptybots MCP?

No package is declared in the MCP registry: clone the uptybots/mcp-server repository, follow its README, then declare the start command in your client's MCP configuration.

Is Uptybots MCP free?

The code is published under the MIT licence and can be used free of charge.

Is Uptybots MCP safe?

No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.

Is it an official server?

Yes: the awesome-mcp-servers list marks it as the service vendor's official implementation.

What are the alternatives to Uptybots MCP?

In the same category: Netdata, MCP grafana, Openstatus, and OneUptime. Netdata and MCP grafana score higher on our grid.

Related articles

Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score