Model Context Protocol server for Rollbar
API Status Check is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Live status probes plus published uptime and incident history for 280+ APIs and cloud services.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http api-status-check-mcp https://apistatuscheck.com/api/mcp
# 2 — ask your agent for something these tools do
# list_apis, search_apis, get_api_status and 5 more
API Status Check costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http api-status-check-mcp https://apistatuscheck.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Category slug to filter by, e.g. "ai" — omit for all categories. |
| limit | integer | no | Max results (default 25). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query, e.g. "openai" or "payments". |
| limit | integer | no | Max results (default 25). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | API slug, e.g. "openai". Use search_apis to resolve a name. |
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.
No parameter schema on file.
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%.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | API slug, e.g. "openai". |
| range | string | no | Window to return data points for (default 24h). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | API slug, e.g. "openai". Use search_apis to resolve a name. |
| window | string | no | Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d). |
| limit | integer | no | Max incidents (default 25). |
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 rank
| Parameter | Type | Required | Notes |
|---|---|---|---|
| services | array | yes | API slugs to compare, e.g. ["openai","anthropic","vercel"]. |
| window | string | no | Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d). |
Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install API Status Check or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish API Status Check can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.