content(mcp): add API Status Check MCP server

[shibley]

Adds one entry: content/mcp/api-status-check-mcp-server.mdx.

What it is. A remote MCP server that answers "is this third-party API actually down, or is the bug mine?" — 285 public APIs and developer platforms across 29 categories. Streamable HTTP, stateless, read-only, no auth of any kind (no account, no key, no Authorization header).

claude mcp add --transport http apistatuscheck https://apistatuscheck.com/api/mcp

Everything in the entry is reproducible without an account. Rather than asking you to take the numbers on trust, the entry body carries the three commands that produce them, and I ran them today (2026-08-15):

curl -s -X POST https://apistatuscheck.com/api/mcp \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

→ eight tools: list_apis, search_apis, get_api_status, list_down_apis, get_uptime_history, get_incident_history, rank_reliability, list_categories.

curl -s https://apistatuscheck.com/api/status | jq '{count, categories: (.categories | length)}'

→ {"count": 285, "categories": 29} — the two figures quoted in the entry.

Disclosure: this is my own product (Bity LLC), submitted under my own account. Free tier requires no signup; the MCP endpoint itself is not gated.

Safety / privacy, as required by CONTRIBUTING. Disclosed in the frontmatter and worth stating here too: all eight tools are read-only — there is no write, install, package, background-worker or destructive action. The server calls vendors' status endpoints on your behalf and never receives your own API credentials. What leaves your client is the service name or category you asked about; queries hit Bity LLC infrastructure and appear in its request logs like any HTTP request.

Two honesty properties I'd rather you check than assume, since they are the sort of thing a status tool usually gets wrong:

• Freshness is explicit. list_apis/list_down_apis come from an hourly monitor and carry their timestamp; get_api_status also probes at call time and returns both, so a single-region blip surfaces as a disagreement instead of a confirmed outage.
• Absent history reports covered: false, not zero. A service with no incidents on file is not a service with a perfect record, and get_incident_history / rank_reliability say so instead of letting a flattering number stand in for missing data.

Validation. node scripts/validate-content.mjs and node scripts/validate-content.mjs --strict-recommended both pass — Validated 1387 content files. Content validation passed. — with zero warnings attributed to this file (the 24 pre-existing warnings are all skills/*.mdx, untouched here).

Content-only, single entry, no generated files: README.md, apps/web/public/data/**, apps/web/src/generated/**, routeTree.gen.ts and apps/web/public/downloads/** are untouched, and pnpm-lock.yaml was reverted after a local install so the diff is exactly one new file. No visual impact beyond the entry rendering in mcp.

Happy to reword, trim the body, or drop fields if the house style prefers something shorter.