io.github.aistatusdashboard/aistatusdashboard

MCPcommunity
v1.0.1io.github.aistatusdashboardUnknownUpdated 5mo agoGitHub

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

A real-time status dashboard for AI service providers (OpenAI, Anthropic, Google Gemini, etc.). Real-time Status Monitoring: Active checks via . Historical Data: Firestore-backed history and incident logging. Analytics: Dashboard for uptime, response times, and costs. Notifications: Email alerts via SMTP (Nodemailer) and Webhooks. Stack: Next.js (App Router), Tailwind CSS, Firebase Firestore.…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.aistatusdashboard
LicenseUnknown
Version1.0.1
Sourcemcp-registry
GitHubaistatusdashboard/aistatusdashboard
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—CVE scan · not run+0/30
→ Not yet scanned — package must be on npm
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 19d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

A real-time status dashboard for AI service providers (OpenAI, Anthropic, Google Gemini, etc.). Real-time Status Monitoring: Active checks via . Historical Data: Firestore-backed history and incident logging. Analytics: Dashboard for uptime, response times, and costs. Notifications: Email alerts via SMTP (Nodemailer) and Webhooks. Stack: Next.js (App Router), Tailwind CSS, Firebase Firestore. Firebase Project (Firestore enabled) 1. Clone the repository 2. Install dependencies: 3. Copy to and…

Keywords
mcp