Search / io.github.shibley/apistatuscheck
protogridR0· no sign-inLive status probes plus published uptime and incident history for 280+ APIs and cloud services.
v0.2.3 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"apistatuscheck": {
"type": "http",
"url": "https://apistatuscheck.com/api/mcp"
}
}
}claude mcp add --transport http apistatuscheck https://apistatuscheck.com/api/mcp[mcp_servers.apistatuscheck]
url = "https://apistatuscheck.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"apistatuscheck": {
"type": "remote",
"url": "https://apistatuscheck.com/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"apistatuscheck": {
"type": "http",
"url": "https://apistatuscheck.com/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=apistatuscheck&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpc3RhdHVzY2hlY2suY29tL2FwaS9tY3AifQ%3D%3D"
}{
"servers": {
"apistatuscheck": {
"type": "http",
"url": "https://apistatuscheck.com/api/mcp"
}
}
}{
"mcpServers": {
"apistatuscheck": {
"httpUrl": "https://apistatuscheck.com/api/mcp"
}
}
}extensions:
"apistatuscheck":
enabled: true
name: "apistatuscheck"
type: streamable_http
uri: "https://apistatuscheck.com/api/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_categories (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_api_status (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_uptime_history (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …tools.token_costabout 1,085 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-40d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://apistatuscheck.com/api/mcp streamable-http | none | yes | 100% | 243 ms | 2025-11-25 | 2026-10-20 |
get_api_status | 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_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. |
get_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%. |
list_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. |
list_categories | Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis. |
list_down_apis | 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. |
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. 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. |
search_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. |
Schemas: list_tools.
{
"name": "io.github.shibley/apistatuscheck",
"title": "API Status Check",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://apistatuscheck.com/api/mcp",
"type": "streamable-http"
}
],
"version": "0.2.3",
"repository": {
"id": "1167362967",
"url": "https://github.com/shibley/apistatuscheck-mcp-server",
"source": "github"
},
"websiteUrl": "https://apistatuscheck.com",
"description": "Live status probes plus published uptime and incident history for 280+ APIs and cloud services."
}