Is the API Status Check MCP server down?

mcp-registry/io.github.shibley/apistatuscheck · registry v0.2.3 · server reports v0.1.0

Also listed as awesome/shibley/apistatuscheck-mcp-server

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 13:02 UTC · handshake 645ms

As of 2026-11-22 13:02 UTC, the API Status Check MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
100%
checks observed
6,865
outages (90d)
2
tools
8

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

Point your MCP client at this streamable-http endpoint: https://apistatuscheck.com/api/mcp

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 8 tool(s); ~1,298 tokens of tool definitions.
Scores higher than 37% of 27,586 MCP servers Glimind has audited.
Its tool list costs an agent ~1,298 tokens per session — lighter than 60% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Descriptions100
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (2)

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_api_status, get_incident_history, get_uptime_history, list_apis, list_categories and 3 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.shibley%2Fapistatuscheck/fixes

get_api_status 1 change
{
  "name": "get_api_status",
  "description": "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.",
  "inputSchema": {
    "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."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check an API right now"
}
get_incident_history 1 change
{
  "name": "get_incident_history",
  "description": "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.",
  "inputSchema": {
    "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."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a service’s published incident history"
}
get_uptime_history 1 change
{
  "name": "get_uptime_history",
  "description": "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%.",
  "inputSchema": {
    "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)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get retained uptime history"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.shibley/apistatuscheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.shibley/apistatuscheck"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.shibley%2Fapistatuscheck.svg)](https://glimind.com/server/mcp-registry%2Fio.github.shibley%2Fapistatuscheck?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.shibley%2Fapistatuscheck?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.shibley%2Fapistatuscheck.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4cdedf7a0bdd60c7…, first seen 2026-10-17, included at leaf 15151 of 383,839. Version history · verify what your client received.

Tools (8)

Compare: most reliable devops servers · most reliable knowledge servers · most reliable monitoring servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the API Status Check MCP server down right now?

As of 2026-11-22 13:02 UTC, the API Status Check MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.

How many tools does API Status Check MCP server provide?

API Status Check MCP server advertises 8 tools, including get_api_status, get_incident_history, get_uptime_history, list_apis, list_categories.

How do I install API Status Check MCP server?

Point your MCP client at this streamable-http endpoint: https://apistatuscheck.com/api/mcp

Is the API Status Check MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of API Status Check MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve