FRENES

Monitoring and observability · MCP server

Openstatus: MCP server, setup and security

Openstatus is an open-source MCP server that lets an AI agent manage monitors, status pages, incidents, and maintenance in openstatus. Its repository has 9,221 stars and its last commit is from October 24, 2026 and it is licensed under AGPL-3.0.

Actively maintainedRemote serverTop 10% by stars

What Openstatus does

According to its repository: “Manage monitors, status pages, incidents and maintenances in your openstatus workspace.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Openstatus is listed under Monitoring and observability, a category of 57 servers in the directory, where it ranks #2 by stars.

Topics declared by the repository: observability, open-source, status-page, turso, tinybird, monitoring.

Installing and connecting Openstatus

Distribution modes declared in the official MCP registry:

  • remote server (streamable-http): you connect to it by URL, with nothing to install locally

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Openstatus. 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 June 19, 2023, the openstatusHQ/openstatus repository has 9,221 stars and 794 forks, with 31 open issues. It has more stars than 98% of the servers in the directory. It received changes this month. Version published in the registry: 1.0.0 (September 10, 2026).

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 : 261261
GitHub stars of the most followed servers in the category (log scale); Openstatus in orange. Checked October 25, 2026.

Verdict

Openstatus is one of the most solid servers in its category: followed, maintained and well framed.

Strengths

  • Active project: recent commit
  • Widely followed: 9.2K stars
  • Listed in the official MCP registry
  • Usable remotely, without installation

Frequently asked questions

How do I install Openstatus?

Openstatus is distributed as a remote server. Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of openstatusHQ/openstatus.

Is Openstatus free?

The code is published under the AGPL-3.0 licence and can be used free of charge.

Is Openstatus 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?

It is published in the MCP registry under the verified namespace dev.openstatus, which shows the publisher controls that domain.

What are the alternatives to Openstatus?

In the same category: Netdata, MCP grafana, OneUptime, and Homebutler.

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