MCP.Market

API Status Check MCP server

online · 100% uptime
by shibley·io.github.shibley/apistatuscheck·v0.2.3·1 stars
No reviews yet

Live status probes plus published uptime and incident history for 280+ APIs and cloud services.

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed API Status Check yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

API Status Check tools (8)

write = sends, deletes, buys or posts
  • get_api_statusFree

    Probe a monitored API endpoint at call time and return up/degraded/down with the response time. This is the tool to reach for when a user asks "is X down?" — it makes a real request rather than reading the hourly cache.

  • get_incident_historyFree

    Real incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page. Use this for "has X been flaky lately?" — it is the vendor’s own record, not our probes. Services without a public Statuspage endpoint return covered:false rather than an empty list.

  • get_uptime_historyFree

    Uptime percentages, response-time stats and recorded data points for one API over a time range. History is retained for 30 days; an API added recently will have few or no data points, which reads as null percentages rather than 100%.

  • list_apisFree

    List the APIs and developer platforms this service monitors, optionally filtered by category. Statuses come from the most recently published monitor snapshot, not a live probe, and can be up to a day old — check monitorCheckedAt, and call get_api_status when the caller needs the status right now.

  • list_categoriesFree

    Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.

  • list_down_apisFree

    Everything the most recent monitor run found down or degraded, across all categories. Returns an empty list when the monitor snapshot is missing or stale — an empty list is therefore not proof that everything is healthy; check monitorLastRun.

  • rank_reliabilityFree

    Given several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window. Use this to answer "which vendor in my stack is least reliable?" — it compares services across vendors, which a vendor’s own monitoring tool cannot. Services with no archive are listed separately as uncovered instead of being ranked as flawless.

  • search_apisFree

    Find monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 695ms20/20
  • Tool poisoning8 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 22 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How API Status Check compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
210 ms
faster than 62% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 8 read

Install API Status Check in Claude Code, Cursor or VS Code

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

What the publisher says

From the API Status Check repository's README, as published. We do not edit it. Read it on GitHub

API Status Check MCP Server

An MCP (Model Context Protocol) server for checking real-time operational status of 285 cloud services and APIs directly from AI coding assistants.

Features

Supported Services

AWS, GitHub, Stripe, OpenAI, Vercel, Cloudflare, Datadog, PagerDuty, Twilio, Shopify, Slack, Zoom, and 270+ more. Full list at apistatuscheck.com.

Quick Start

Hosted endpoint (recommended — nothing to install)

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.

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

For stdio-only clients:

npx -y mcp-remote https://apistatuscheck.com/api/mcp

Using npx

npx -y apistatuscheck-mcp-server

Broken on published version 0.1.0. That tarball's dist/index.js shipped

without a #!/usr/bin/env node shebang, so the shim was executed by sh

instead of Node and the command failed with command not found. Fixed in this

repo (shebang added, plus an apistatuscheck-mcp-server bin alias so the

command matches the package name), but the fix is not on npm yet — 0.1.1

needs to be published. Until then, build from source:

bash

git clone https://github.com/shibley/apistatuscheck-mcp-server.git

cd apistatuscheck-mcp-server && npm install && npm run build

node dist/index.js

Using Docker

docker build -t apistatuscheck-mcp .
docker run -i apistatuscheck-mcp

Configuration

Claude Desktop

Add to your claudedesktopconfig.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.

{
  "mcpServers": {
    "apistatuscheck": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://apistatuscheck.com/api/mcp"]
    }
  }
}

Cursor / Other MCP Clients

Same hosted endpoint via mcp-remote:

{
  "mcpServers": {
    "apistatuscheck": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://apistatuscheck.com/api/mcp"]
    }
  }
}

Environment Variables

Local Development

git clone https://github.com/shibley/apistatuscheck-mcp-server.git
cd apistatuscheck-mcp-server
npm install
npm run build
node dist/index.js

License

MIT — Bity LLC

Nothing above is checked by us. What we check is on the safety report.

API Status Check: common questions

Is API Status Check MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the API Status Check safety report
How do I install API Status Check?
It runs remotely at apistatuscheck.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does API Status Check need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is API Status Check maintained?
The last commit was 55 days ago (2026-09-09). The latest release is v0.2.3.
Is API Status Check up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does API Status Check compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from shibley →