The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Apistatuscheck MCP Server listing page.
An MCP (Model Context Protocol) server for checking real-time operational status of 285 cloud services and APIs directly from AI coding assistants.
| Tool | Description |
|---|---|
check_status | Check the status of a specific API (e.g. github, openai, stripe) |
list_apis | List all monitored APIs and their current status |
list_categories | List available service categories (cloud, payments, etc.) |
check_category | Check all APIs in a specific category |
check_url | Check any public URL for availability |
AWS, GitHub, Stripe, OpenAI, Vercel, Cloudflare, Datadog, PagerDuty, Twilio, Shopify, Slack, Zoom, and 270+ more. Full list at apistatuscheck.com.
The server is also hosted, so the fastest path is the remote Streamable HTTP
endpoint. This is the same entry the official MCP Registry advertises as
io.github.shibley/apistatuscheck.
For stdio-only clients:
Broken on published version
0.1.0. That tarball'sdist/index.jsshipped without a#!/usr/bin/env nodeshebang, so the shim was executed byshinstead of Node and the command failed withcommand not found. Fixed in this repo (shebang added, plus anapistatuscheck-mcp-serverbin alias so the command matches the package name), but the fix is not on npm yet —0.1.1needs to be published. Until then, build from source:
Add to your claude_desktop_config.json. This points at the hosted endpoint —
do not use "args": ["-y", "apistatuscheck-mcp-server"], because the only version
on npm (0.1.0) is the broken one described above and fails silently.
Same hosted endpoint via mcp-remote:
| Variable | Default | Description |
|---|---|---|
ASC_BASE_URL | https://apistatuscheck.com | Base URL for the API |
MIT — Bity LLC