API Status Check MCP

This MCP server allows AI agents to check the real-time operational status of over 285 cloud services and APIs. It provides tools to check specific API status, list all monitored APIs, list service categories, check all APIs in a category, and verify public URL availability. It supports major services like AWS, GitHub, Stripe, and OpenAI.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Bity LLC

MCP endpoint (Streamable HTTP)

https://apistatuscheck.com/api/mcp

Vendor documentation

What its tools do

8 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (8)

list_apis
search_apis
get_api_status
list_down_apis
get_uptime_history
get_incident_history
rank_reliability
list_categories

8 of 8 have a description · 0 of 8 declare behavior hints · 6 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 7:22 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Check the status of a specific API like GitHub or Stripe
List all monitored APIs and their current status
Check all APIs in a specific category such as cloud or payments
Check any public URL for availability

Source and maintenance

Community listingRegistry 0.2.3

mcp-registry: io.github.shibley/apistatuscheck@0.2.3 Source repository Project website

Maintenance checked: Nov 6, 2026, 6:33 PM UTC

Protocol and capabilities

Server: apistatuscheck 0.1.0
MCP protocol negotiated in check: 2025-11-25
Tools: 8 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Live and historical availability for public APIs and developer platforms. Use get_api_status when the user hits an error from a third-party API and you need to tell an outage apart from a bug in their own code. Statuses from list_apis and list_down_apis are a published snapshot that can be up to a day old and carry a monitorCheckedAt timestamp — read it before relying on them; get_api_status probes the endpoint at call time. For past behaviour rather than the present, use get_incident_history (the vendor’s own published incidents) and rank_reliability (cross-vendor scorecard — incidents, downtime minutes and MTTR for several services at once, which no single vendor’s tooling can answer). Both report covered:false for services we hold no archive on; treat that as unknown, never as zero.

Tools

8 advertised

list_apis — List monitored APIs

Advertised by the server during the last successful anonymous check.

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_apis input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 25)."
    },
    "category": {
      "type": "string",
      "description": "Category slug to filter by, e.g. \"ai\" — omit for all categories."
    }
  }
}

search_apis — Search monitored APIs

Advertised by the server during the last successful anonymous check.

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.

search_apis input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 25)."
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "Free-text query, e.g. \"openai\" or \"payments\"."
    }
  }
}

get_api_status — Check an API right now

Advertised by the server during the last successful anonymous check.

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_api_status input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "description": "API slug, e.g. \"openai\". Use search_apis to resolve a name."
    }
  }
}

list_down_apis — List APIs currently down or degraded

Advertised by the server during the last successful anonymous check.

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.

list_down_apis input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

get_uptime_history — Get retained uptime history

Advertised by the server during the last successful anonymous check.

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

get_uptime_history input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "description": "API slug, e.g. \"openai\"."
    },
    "range": {
      "enum": [
        "24h",
        "7d",
        "30d"
      ],
      "type": "string",
      "description": "Window to return data points for (default 24h)."
    }
  }
}

get_incident_history — Get a service’s published incident history

Advertised by the server during the last successful anonymous check.

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_incident_history input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "service"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max incidents (default 25)."
    },
    "window": {
      "enum": [
        "7d",
        "30d",
        "90d",
        "180d",
        "365d",
        "all"
      ],
      "type": "string",
      "description": "Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d)."
    },
    "service": {
      "type": "string",
      "minLength": 1,
      "description": "API slug, e.g. \"openai\". Use search_apis to resolve a name."
    }
  }
}

rank_reliability — Rank vendors by reliability

Advertised by the server during the last successful anonymous check.

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.

rank_reliability input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "services"
  ],
  "properties": {
    "window": {
      "enum": [
        "7d",
        "30d",
        "90d",
        "180d",
        "365d",
        "all"
      ],
      "type": "string",
      "description": "Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d)."
    },
    "services": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "maxItems": 25,
      "minItems": 1,
      "description": "API slugs to compare, e.g. [\"openai\",\"anthropic\",\"vercel\"]."
    }
  }
}

list_categories — List API categories

Advertised by the server during the last successful anonymous check.

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

list_categories input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 583 ms
95th percentile latency: 583 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 7:22 PM UTC · probe · passed · 583 ms · metadata changed · 8 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add api-status-check-mcp --url https://apistatuscheck.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable api-status-check-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start api-status-check-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http api-status-check-mcp https://apistatuscheck.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://apistatuscheck.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "api-status-check-mcp": {
      "serverUrl": "https://apistatuscheck.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like API Status Check MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows