io.github.shibley由 GitHub 账号 shibley 发布v0.2.3更新于 Oct 25, 2026
Live status probes plus published uptime and incident history for 280+ APIs and cloud services.
远程 MCP 服务器，让助手查询 280 多个云 API 和服务的实时状态、可用率历史与厂商事故记录。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.shibley%2Fapistatuscheck/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"api-status-check": {
"type": "http",
"url": "https://apistatuscheck.com/api/mcp"
}
}
}An MCP (Model Context Protocol) server for checking real-time operational status of 285 cloud services and APIs directly from AI coding assistants.
AWS, GitHub, Stripe, OpenAI, Vercel, Cloudflare, Datadog, PagerDuty, Twilio, Shopify, Slack, Zoom, and 270+ more. Full list at apistatuscheck.com.
The server is also hosted, so the fastest path is the remote Streamable HTTP
endpoint. This is the same entry the official MCP Registry advertises as
io.github.shibley/apistatuscheck.
For stdio-only clients:
Broken on published version
0.1.0. That tarball'sdist/index.jsshipped without a#!/usr/bin/env nodeshebang, so the shim was executed byshinstead of Node and the command failed withcommand not found. Fixed in this repo (shebang added, plus anapistatuscheck-mcp-serverbin alias so the command matches the package name), but the fix is not on npm yet —0.1.1needs to be published. Until then, build from source:
Add to your claude_desktop_config.json. This points at the hosted endpoint —
do not use "args": ["-y", "apistatuscheck-mcp-server"], because the only version
on npm (0.1.0) is the broken one described above and fails silently.
Same hosted endpoint via mcp-remote:
MIT — Bity LLC
来源：README.md，提交 a51dd62
List monitored APIs
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.
limitcategorySearch monitored APIs
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.
limitquery必填Check an API right now
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.
slug必填List APIs currently down or degraded
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.
无需输入参数。
Get retained uptime history
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%.
slug必填rangeGet a service’s published 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. 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.
limitwindowservice必填Rank vendors by 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. 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.
windowservices必填List API categories
Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
无需输入参数。
已满足适用检查项的 100%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
tattoo.check官方发布者
check.tattoo: tattoo size and placement guide 的托管 MCP 服务，由 check.tattoo 发布；无需登录；Streamable HTTP；5 个工具。
pt.iva官方发布者
在 VIES 中校验欧盟增值税号，并返回葡萄牙增值税法典（CIVA）与 RITI 条文，支持葡语和英语。
由 GitHub 账号 throttler300 发布
一个本地 MCP 服务器，将助手的引用绑定到已准入的源文本并标注片段位置，可选拒绝哈希过期的引用。
由 GitHub 账号 kriton-dev 发布
托管在 Apify 上的远程 MCP 服务器，让助手检查网站声明的七类 HTTP 安全响应头，且不返回原始头值。
由 GitHub 账号 Voopa-Corp 发布
对照创作要求审查已生成的视频，在再次付费渲染前建议是剪辑修改、重试一次还是更换方案。
claude mcp add --transport http apistatuscheck https://apistatuscheck.com/api/mcpnpx -y mcp-remote https://apistatuscheck.com/api/mcpnpx -y apistatuscheck-mcp-servergit clone https://github.com/shibley/apistatuscheck-mcp-server.gitcd apistatuscheck-mcp-server && npm install && npm run buildnode dist/index.jsdocker build -t apistatuscheck-mcp .docker run -i apistatuscheck-mcp{ "mcpServers": { "apistatuscheck": { "command": "npx", "args": ["-y", "mcp-remote", "https://apistatuscheck.com/api/mcp"] } }}{ "mcpServers": { "apistatuscheck": { "command": "npx", "args": ["-y", "mcp-remote", "https://apistatuscheck.com/api/mcp"] } }}git clone https://github.com/shibley/apistatuscheck-mcp-server.gitcd apistatuscheck-mcp-servernpm installnpm run buildnode dist/index.js