Developer · Remote MCP server
API Status Check
Live status probes plus published uptime and incident history for 280+ APIs and cloud services.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.shibley/apistatuscheck- Version
- 0.2.3
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-09
- Updated
- 2026-09-09
- Publisher
- shibley (GitHub) · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/shibley) · how
- Website
- apistatuscheck.com
- Repository
- github.com/shibley/apistatuscheck-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://apistatuscheck.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- apistatuscheck 0.1.0 · protocol 2025-06-18
- Tools discovered
- 8:
list_apis,search_apis,get_api_status,list_down_apis,get_uptime_history,get_incident_history,rank_reliability,list_categories - Checked on
- 2026-10-05
How to connect API Status Check
API Status Check is a remote MCP server: there is nothing to install. Its endpoint is https://apistatuscheck.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from shibley (GitHub)
| Server | Runs |
|---|---|
| AIDataParserPDFs, images and messy text to schema-guaranteed JSON. try_parse runs a real extraction, no key. | Remote · HTTPLive check: ✓ handshake |
| AISOToolsSearch, compare, and find alternatives across a catalog of 3,000+ AI tools. | Remote · HTTPLive check: ✓ handshake |
| MyMCPToolsFind MCP servers and check whether they actually respond, via live handshake probes. | Remote · HTTPLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| Apex (smartapex.uk) AI Component Card StoreRun verified read-only code tools: quant diagnostics + agent-ops preflight, no source exposure. | Remote · HTTPLive check: ✓ handshake |
| APEX PSICryptographic truth infrastructure for AI agents: seal, verify, anchor, cite, audit. | Local · stdio |
| API Key CaseLocal MCP tools for secret status and guarded deployment. Values never reach the agent. | Local · stdio |
| API LockerEncrypted credential vault: LLM, service & OAuth keys. 21-tool MCP server for your AI agent. | Local · stdio |
| Api TesterMCP server for API testing: HTTP requests, cURL generation, health checks. | Local · stdio |
| api-changelogSDK breaking-change tracker for AI agents - Anthropic/OpenAI/LangChain/MCP/Mistral. | Local · stdio |
| API.market MCP GatewayConnect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies. | Remote · HTTPLive check: sign-in required |
| ApibaseMCP endpoint to APIbase catalog (https://apibase.pro/llms.txt). USDC: x402 Base, MPP Tempo. | Remote & Local · HTTP, stdioLive check: ✓ handshake |