Skip to content

API Status Check

by shibley · remote · no sign-in to list tools · v0.2.3 · published by GitHub user shibley

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

Changes · 1
CompareRegistry entry

8 tools: 1 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 1Claude Code: ask
  • rank_reliabilityGiven 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 7Claude Code: allow
  • get_api_statusProbe a monitored API endpoint at call time and return up/degraded/down with the response time.No findings

    Why it is in this group

    • The name "get_api_status" says "get": a word for reading.
    Description, as the server wrote it
    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_historyReal 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.No findings

    Why it is in this group

    • The name "get_incident_history" says "get": a word for reading.
    Description, as the server wrote it
    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_historyUptime percentages, response-time stats and recorded data points for one API over a time range.No findings

    Why it is in this group

    • The name "get_uptime_history" says "get": a word for reading.
    Description, as the server wrote it
    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_apisList the APIs and developer platforms this service monitors, optionally filtered by category.No findings

    Why it is in this group

    • The name "list_apis" says "list": a word for reading.
    Description, as the server wrote it
    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_categoriesCategory slugs and how many monitored APIs sit in each.No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
  • list_down_apisEverything the most recent monitor run found down or degraded, across all categories.No findings

    Why it is in this group

    • The name "list_down_apis" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • search_apisFind monitored APIs by name, slug, category or description.No findings

    Why it is in this group

    • The name "search_apis" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.3. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__apistatuscheck__list_apis",
      "mcp__apistatuscheck__search_apis",
      "mcp__apistatuscheck__get_api_status",
      "mcp__apistatuscheck__list_down_apis",
      "mcp__apistatuscheck__get_uptime_history",
      "mcp__apistatuscheck__get_incident_history",
      "mcp__apistatuscheck__list_categories"
    ],
    "ask": [
      "mcp__apistatuscheck__rank_reliability"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as apistatuscheck. Review it before you use it.