API Tools

apistatuscheck.com

Monitors the status and uptime of monitored APIs, offering search, status probes, and uptime history.

1 endpoint8 known toolsFirst detected May 29, 2026Last detected September 6, 2026

ENDPOINT 1

https://apistatuscheck.com/api/mcp

No auth detected

MCP server metadata

Name: apistatuscheck
Version: 0.1.0

Capabilities

tools.listChanged

Server instructions

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 come from an hourly monitor and carry a timestamp; 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.

Known tools 8

list_apis

List the APIs and developer platforms this service monitors, optionally filtered by category.

Inferred read-only

search_apis

Find monitored APIs by name, slug, category or description.

Inferred read-only

get_api_status

Probe a monitored API endpoint at call time and return up/degraded/down with the response time.

Inferred read-only

list_down_apis

Everything the most recent monitor run found down or degraded, across all categories.

Inferred read-only

get_uptime_history

Uptime percentages, response-time stats and recorded data points for one API over a time range.

Inferred read-only

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

Inferred read-only

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

Inferred read-only

list_categories

Category slugs and how many monitored APIs sit in each.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.apistatuscheck]
url = "https://apistatuscheck.com/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: apistatuscheck
Remote MCP URL: https://apistatuscheck.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "apistatuscheck",
  "transport": "streamable-http",
  "url": "https://apistatuscheck.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for apistatuscheck.com was fetched 2026-08-04T00:39:04.593Z and is being refreshed.

Trust status Trusted

apistatuscheck.com is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.