Back to Browse

Aistatusdashboard MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://aistatusdashboard.com/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

7 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

clipboard

Check that this permission is expected for this type of plugin.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-aistatusdashboard-aistatusdashboard": {
      "url": "https://aistatusdashboard.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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.

Pages

  • / — live board for all monitored apps, troubled apps sort first
  • /<app-id> — per-app verdict page (e.g. /chatgpt, /claude)
  • /incidents — outage history with per-incident detail
  • /how-it-works, /about, /privacy, /terms

Running locally

npm install
cp .env.example .env.local   # add Firebase credentials
npm run dev

Tests and checks:

npm run lint
npm run type-check
npm test          # unit tests (jest)
npm run test:e2e  # playwright

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

Reviews

No reviews yet

Be the first to review this server!