io.github.HappyMealSteak/apizone
Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.
Real-time status & uptime monitoring for 294 popular APIs — is it down, and how reliable?
| Author | io.github.HappyMealSteak |
|---|---|
| Access | remote |
| Publisher key required | No |
| Measured state | Alive, not deep-tested |
| L1 liveness | alive |
| L1 latency | 1881 ms |
| Last measured | 2026-10-26 |
Add to your agent
Copy this into your MCP client config:
{
"mcpServers": {
"apizone": {
"url": "https://apizone.io/api/mcp",
"transport": "streamable-http"
}
}
}
Measured tools (5)
list_apisread-onlyList the APIs APIzone monitors and their current status (operational, degraded, down, or unknown). Optionally filter by category. Use this to discover which APIs are tracked and get a quick health overview.
Parameters:
category— string — Filter to one category. One of: payments, ai, cloud, developer-tools, communication, email, auth, analytics, maps, commerce, social, media, data, finance, gaming, productivity, shipping, web3
Hints: read-only yes · destructive no · idempotent yes · open-world yes
get_api_statusread-onlyCheck whether a specific API is currently up, degraded, or down. Accepts an API name or slug (e.g. 'stripe', 'OpenAI', 'aws s3'). Returns current status, last measured latency, and when it was last checked. Use this to answer 'is X down right now?'.
Parameters:
api(required) — string — API name or slug, e.g. 'stripe', 'OpenAI', 'github'.
Hints: read-only yes · destructive no · idempotent yes · open-world yes
check_apisread-onlyCheck the current status of multiple APIs in one call — useful when diagnosing a failing app that depends on several services (e.g. ['stripe','openai','aws s3']). Returns each API's status so an agent can tell which dependency is the culprit.
Parameters:
apis(required) — array — API names or slugs to check, e.g. ['stripe','openai','github'].
Hints: read-only yes · destructive no · idempotent yes · open-world yes
get_api_uptimeread-onlyGet uptime percentage and latency (median + 95th percentile) for an API over the last 24 hours, 7 days, 30 days, and 90 days. Use this for reliability questions like 'how reliable has Stripe been this month?'.
Parameters:
api(required) — string — API name or slug, e.g. 'stripe', 'openai'.
Hints: read-only yes · destructive no · idempotent yes · open-world yes
list_recent_incidentsread-onlyList recent API outages and degradations detected by APIzone, newest first. Optionally filter by category. Use this to answer 'what APIs have had problems recently?' or to check a category's incident history.
Parameters:
limit— integer — Max incidents to return (1-50).category— string — Filter to one category. One of: payments, ai, cloud, developer-tools, communication, email, auth, analytics, maps, commerce, social, media, data, finance, gaming, productivity, shipping, web3
Hints: read-only yes · destructive no · idempotent yes · open-world yes
Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.