API Status Check

io.github.shibleyPublished by GitHub account shibleyv0.2.3Updated Oct 25, 2026

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

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant check live status, uptime history and vendor incidents for 280+ cloud APIs and services.

What you can do
List and search monitored APIs and their categories, resolving a product name to a slug or filtering by category from the latest monitor snapshot. Probe a specific API endpoint at call time for up, degraded or down with response time. See everything the last monitor run found down or degraded. Retrieve uptime percentages, response-time stats and data points over a time range, plus incidents vendors published on their own status pages. Rank several services worst-first by incident count, downtime, mean time to resolve and longest incident.
When to use it
Useful when an assistant needs to answer whether a service such as GitHub, Stripe or OpenAI is down right now, how reliable it has been over the past month, or which vendor in a stack has the worst incident record.
Requirements
A remote Streamable HTTP endpoint; nothing to install. Stdio-only clients can bridge to it with npx mcp-remote, which needs Node.js. No account, API key or header is declared. An optional ASC_BASE_URL variable overrides the base URL.
Before you install
Statuses from the list tools come from a snapshot that can be up to a day old, and an empty down list can mean a missing or stale snapshot rather than healthy services. Uptime history covers only 30 days, and recently added APIs show null percentages. The README notes the published npm package version 0.1.0 is broken and fails silently, so prefer the hosted endpoint. The README's tool names differ from the server's actual tool list.

Installation

In SourceWeft

  1. Open API Status Check in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.shibley%2Fapistatuscheck/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "api-status-check": {
      "type": "http",
      "url": "https://apistatuscheck.com/api/mcp"
    }
  }
}

README

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

ToolDescription
check_statusCheck the status of a specific API (e.g. github, openai, stripe)
list_apisList all monitored APIs and their current status
list_categoriesList available service categories (cloud, payments, etc.)
check_categoryCheck all APIs in a specific category
check_urlCheck any public URL for availability

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.

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

For stdio-only clients:

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

Using npx

bash
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.gitcd apistatuscheck-mcp-server && npm install && npm run buildnode dist/index.js

Using Docker

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

Configuration

Claude Desktop

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.

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

Cursor / Other MCP Clients

Same hosted endpoint via mcp-remote:

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

Environment Variables

VariableDefaultDescription
ASC_BASE_URLhttps://apistatuscheck.comBase URL for the API

Local Development

bash
git clone https://github.com/shibley/apistatuscheck-mcp-server.gitcd apistatuscheck-mcp-servernpm installnpm run buildnode dist/index.js

License

MIT — Bity LLC

Source: README.md at commit a51dd62

Tools

8

list_apis

List monitored APIs

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.

Parameterslimitcategory

search_apis

Search monitored APIs

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.

Parameterslimitqueryrequired

get_api_status

Check an API right now

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.

Parametersslugrequired

list_down_apis

List APIs currently down or degraded

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.

Takes no parameters.

get_uptime_history

Get retained uptime history

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%.

Parametersslugrequiredrange

get_incident_history

Get a service’s published incident history

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.

Parameterslimitwindowservicerequired

rank_reliability

Rank vendors by reliability

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.

Parameterswindowservicesrequired

list_categories

List API categories

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

Takes no parameters.

Version history

1
  1. v0.2.3LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Check integrations