apistatuscheck
Registry code: 00b4e9891051342c
Live and historical availability for public APIs and developer platforms. Use get_api_status when the user hits an error from a third-party API and you need to tell an outage apart from a bug in their own code. Statuses from list_apis and list_down_apis are a published snapshot that can be up to a day old and carry a monitorCheckedAt timestamp — read it before relying on them; get_api_status probes the endpoint at call time. For past behaviour rather than the present, use get_incident_history (the vendor’s own published incidents) and rank_reliability (cross-vendor scorecard — incidents,…
- endpoint
- https://apistatuscheck.com/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is apistatuscheck live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is apistatuscheck free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does apistatuscheck have?
- 8 tools: rank_reliability, get_api_status, get_incident_history, get_uptime_history, search_apis, list_categories, list_apis, list_down_apis.
- Is apistatuscheck safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.8%· all time 99.8%
last good check
of 8 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- check if a third-party api is down
- get api incident history
- compare api reliability
- list currently down apis
- takes → gives
- text → data
- tools
- 8 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_categories reads open 12h ago
Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 lineslist_apis reads open 12h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Max results (default 25)." }, "category": { "type": "string", "description": "Category slug to filter by, e.g. \"ai\" — omit for all categories." } } }arguments 16 lineslist_down_apis reads open 12h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesrank_reliability reads unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "services" ], "properties": { "window": { "enum": [ "7d", "30d", "90d", "180d", "365d", "all" ], "type": "string", "description": "Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d)." }, "services": { "type": "array", "items": { "type": "string", "minLength": 1 }, "maxItems": 25, "minItems": 1, "description": "API slugs to compare, e.g. [\"openai\",\"anthropic\",\"vercel\"]." } } }arguments 31 linesget_api_status reads unknown 1h ago
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.
{ "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." } } }arguments 14 linesget_incident_history reads unknown 1h ago
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.
{ "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." } } }arguments 32 linesget_uptime_history reads unknown 1h ago
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%.
{ "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)." } } }arguments 23 linessearch_apis reads unknown 17h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Max results (default 25)." }, "query": { "type": "string", "minLength": 1, "description": "Free-text query, e.g. \"openai\" or \"payments\"." } } }arguments 20 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id00b4e9891051342c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/00b4e9891051342c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/00b4e9891051342c?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.