1. Conduid
  2. Cloud
  3. Cloud Status
MCP server · Cloud

Cloud Status

Google Cloud Service Health cli and MCP server

Unclaimed last commit a year ago cloud
41Fair

Scored 3 months ago · breakdown

About Cloud Status

Cloud Status is an MCP server published by ghchinoy in the Cloud category: google Cloud Service Health cli and MCP server. It has been installed 0 times through Conduid.

The repository has 1 stars and 0 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx cloud-status

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Cloud Status

Powered by Claude · Grounded in docs

I know everything about Cloud Status. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

cloud-status

A command-line tool and MCP server to check the status of Google Cloud services.

This tool fetches data from the public Google Cloud status pages:

  • Atom Feed: https://status.cloud.google.com/en/feed.atom
  • JSON History: https://status.cloud.google.com/incidents.json

Installation

To install the cloud-status CLI, you can use go install:

go install github.com/ghchinoy/cloud-status@latest

CLI Usage

The CLI provides commands to get the current status and historical incident data.

Get Current Status

To see the most recent updates from the Google Cloud status feed:

cloud-status current

Get Historical Incidents

To get a list of historical incidents:

cloud-status history

You can filter the history with the following flags:

  • --limit: Limit the number of incidents returned (e.g., --limit 5).
  • --service: Filter by a specific service name (e.g., --service "Google Compute Engine").
  • --severity: Filter by severity (e.g., --severity high).

Example:

cloud-status history --service "Google Cloud Storage" --limit 3

MCP Server Usage

The application can also run as an MCP server, exposing its functionality as a tool.

Stdio Mode

To start the server over stdio, use the --mcp flag:

cloud-status --mcp

HTTP Mode

To start the server over HTTP, use the --mcp-http flag with a listen address:

cloud-status --mcp-http :8080

MCP Tool: get_cloud_status

The server exposes a single tool with the following details:

  • Name: get_cloud_status
  • Description: Retrieves status information for Google Cloud services. It can get the current status from the Atom feed or historical incidents from the JSON feed.
  • Parameters:
    • source (string, required): Specifies the data to retrieve. Must be either "current" or "history".
    • service_filter (string, optional): When source is "history", this filters incidents by the exact service name (e.g., "Google Compute Engine").
    • severity_filter (string, optional): When source is "history", this filters incidents by severity (low, medium, high).
    • limit (int, optional): When source is "history", this limits the number of incidents returned.

README mirrored from the source repository 3 months ago. The original is authoritative.

Questions

About Cloud Status

How do I install Cloud Status?

Run npx cloud-status, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Cloud Status safe to use with an AI agent?

Its trust score is 41 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Cloud Status still maintained?

The last commit was a year ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.