mcpbeat

AI Provider Status MCP Server

io.github.lazymac2x/ai-provider-status
answering

AI Provider Status is answering right now. Last checked 6 min ago. It exposes 3 tools. Last commit 17 May 2026.

Cloudflare Workers MCP server: ai-provider-status

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
163 ms
Response time
average over 24h
0
Stars
last commit 17 May 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add ai-provider-status --transport http https://api.lazy-mac.com/ai-provider-status/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai-provider-status": {
      "url": "https://api.lazy-mac.com/ai-provider-status/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ai-provider-status]
url = "https://api.lazy-mac.com/ai-provider-status/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-provider-status": {
      "url": "https://api.lazy-mac.com/ai-provider-status/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ai-provider-status": {
      "url": "https://api.lazy-mac.com/ai-provider-status/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

all
get_all_status
Get real-time status for all AI providers (OpenAI, Anthropic, Google AI). Returns overall health, component status and active incidents.
incidents
get_incidents
Get active incidents across all AI providers. Optionally filter by provider.
provider
get_provider_status
Get real-time status for a single AI provider.

Endpoints

URLTransportStateLatencyChecked
https://api.lazy-mac.com/ai-provider-status/mcp streamable-http answering 252 ms 6 min ago

AI Provider Status — questions

Answers built from our own checks of this server.

What can AI Provider Status do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_all_status, get_incidents, get_provider_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AI Provider Status working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 163 ms. The bar chart above shows every period we have measured.
How do I connect AI Provider Status?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AI Provider Status need an API key?
No. AI Provider Status completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AI Provider Status?
It answers our handshake in 163 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is AI Provider Status open source?
Yes — 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.