AIStatusDashboard

io.github.aistatusdashboardPublished by GitHub account aistatusdashboardv1.0.1Updated Oct 24, 2026

Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.

The publisher's own server: status.live national parks

VerifiedStreamable HTTPWeb executableSecurity & Monitoring AI & ML

Server details

Identifier: io.github.aistatusdashboard/aistatusdashboard
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account aistatusdashboard for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.aistatusdashboard%2Faistatusdashboard.svg)](https://sourceweft.com/mcp/io.github.aistatusdashboard%2Faistatusdashboard?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A read-only remote MCP server that lets an assistant check AI service status, incidents, metrics and fallback recommendations from AIStatusDashboard.

What you can do: Look up current status and verdicts for monitored AI apps such as ChatGPT, Claude, Gemini, Grok and Copilot, including whether an outage is widespread or local to the user. Review incident history and per-incident detail, with links back to the original provider sources. Read latency and error metrics gathered from the service's own periodic probes. Get fallback recommendations when a provider is troubled. All access is read-only; nothing is written back.
When to use it: Useful when a user asks whether an AI app is down, whether an outage is on their side, or which alternative service to try while a provider is degraded. Also handy for quickly checking incident history or probe metrics before blaming local setup.
Requirements: A remote streamable HTTP endpoint at the provider's site; no package, account, API key or environment variable is declared. Network access to the endpoint is required.

Before you install

Status and verdicts are third-party assessments based on the provider's own probes, official incident feeds and visitor reports, so they may lag or be incomplete; confirm against the official status page for critical decisions. The server is described as read-only, so no data should be changed through it.

Installation

In SourceWeft

Open AIStatusDashboard in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.aistatusdashboard%2Faistatusdashboard/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "aistatusdashboard": {
      "type": "http",
      "url": "https://aistatusdashboard.com/mcp"
    }
  }
}

README

AI Status

Is ChatGPT down, or is it just you?

AI Status answers that one question, fast, for the AI apps people actually use: ChatGPT, Claude, Gemini, Grok, Perplexity, DeepSeek, Meta AI, GitHub Copilot, Cursor, Character.AI, and Le Chat.

What makes it different from mirroring an official status page:

We test the services ourselves. Cron-driven probes send real requests to each provider every few minutes and record latency and errors (lib/services/provider-probes.ts).
We read the official incident feeds for every provider and link to the original source on each incident (lib/services/source-ingestion.ts).
Visitors report in. A one-tap "it's broken for me too" button feeds the "is it just you?" verdict, with self-test traffic filtered out.
We never fake a green light. If a status can't be verified it renders as "checking", not "operational".

Stack

Next.js (App Router) · Tailwind CSS · Firebase Firestore · Firebase App Hosting.

Running locally

Tests and checks:

Data pipeline

Cron routes under /api/cron/* (protected by CRON_SECRET) poll status pages, run live probes, ingest incident feeds, classify community reports, and send email alerts. Schedules live in Cloud Scheduler; results land in Firestore (incidents, synthetic_probes, casual_reports, provider_status, …).

License

MIT

Source: README.md at commit 3ff0290

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts