Apizone

io.github.HappyMealSteakPublished by GitHub account HappyMealSteakv1.0.1Updated Oct 24, 2026

Real-time status & uptime monitoring for 294 popular APIs — is it down, and how reliable?

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant check whether popular third-party APIs are up, degraded or down, and how reliable they have been.

What you can do
  • List monitored APIs and their current status, optionally filtered by category
  • Check one API's live status, last measured latency and time of last check
  • Check several APIs in one call to find which dependency is failing
  • Get uptime percentage and median/95th-percentile latency over 24h, 7d, 30d and 90d
  • List recent outages and degradations, newest first, optionally by category
When to use it
Useful when an assistant is debugging a failing app or integration and needs to know whether a third-party dependency is currently down, or when someone asks how reliable a service has been recently. It answers status questions mid-task without leaving the conversation.
Requirements
A remote Streamable-HTTP endpoint; no install, build or API key is needed. The README states the server is hosted and stateless and that all tools are read-only and require no authentication.
Before you install
Status comes from APIzone's own synthetic probes of public endpoints, not from vendor status pages, so it may differ from official reports. The README notes a public JSON API is limited to 60 requests per minute per IP. No credentials are requested.

Installation

In SourceWeft

  1. Open Apizone in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.HappyMealSteak%2Fapizone/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "apizone": {
      "type": "http",
      "url": "https://apizone.io/api/mcp"
    }
  }
}

README

APIzone — MCP server for API status

Is that API down? APIzone is independent, real-time status monitoring for 294 popular APIs — Stripe, OpenAI, AWS, GitHub, Twilio and more. It runs its own probes from independent infrastructure, so status reflects what's actually observed, not what a vendor's status page reports.

This repository is the public home of APIzone's Model Context Protocol (MCP) server, so any AI agent — Claude, Cursor, or your own — can natively answer "is X down right now?" mid-task.

🔗 apizone.io · Status board · Incidents · API docs · MCP guide

Live examples (these badges update automatically):

[Stripe API status] [OpenAI API status] [GitHub API status]

Connect the MCP server

The server is hosted and stateless — no install, no build, no API key:

bash
claude mcp add --transport http apizone https://apizone.io/api/mcp

Or point any MCP client at the Streamable-HTTP endpoint directly:

https://apizone.io/api/mcp

The server.json in this repo is the Model Context Protocol registry manifest.

Tools

All tools are read-only and require no authentication:

ToolWhat it answers
list_apisWhich APIs are monitored, and their current status (optionally by category)
get_api_statusIs a specific API up, degraded, or down right now?
check_apisStatus of several APIs at once — find which dependency is the culprit
get_api_uptimeUptime % and latency (p50/p95) over 24h / 7d / 30d / 90d
list_recent_incidentsRecent outages and degradations, newest first

Agent discovery is also published at /llms.txt.

Embed a status widget

Drop a live status widget into any page:

html
<div data-apizone="stripe,openai,aws-s3"></div><script src="https://apizone.io/widget.js" async></script>

Or a single badge: https://apizone.io/badge/<slug>.svg — generator at /badges, multi-API widget at /widget.

Public JSON API

No key required; 60 req/min per IP:

  • GET /api/v1/status — all services with current status + latency
  • GET /api/v1/status/<slug> — one API: 24h checks, 90-day uptime, incidents
  • GET /api/v1/uptime/<slug> — uptime % and latency over 24h / 7d / 30d / 90d

Spec at /openapi.json; full reference at /api-docs.

How status is derived

  • Synthetic checks. APIzone probes a public, unauthenticated endpoint of every monitored service. Any HTTP response under 500 counts as healthy (a 401 from api.stripe.com still proves the API is up); timeouts, network errors, and 5xx are failures.
  • Status. Down = recent checks all failing. Degraded = some recent failures, or latency well above the service's own baseline.
  • False-positive protection. Before opening an incident, the checker re-probes once; a transient blip that recovers is suppressed, so it never alerts subscribers.
  • Independent. Status reflects APIzone's own probes and may differ from a vendor's official status page.

About this repository

This is the public MCP + product home for APIzone. The monitoring service itself is hosted at apizone.io; the application source is maintained privately. Issues and suggestions for the MCP server (missing APIs, tool ideas) are welcome here.

License

MIT — see LICENSE. This covers the public docs and registry manifest in this repository; the APIzone service itself is proprietary.

Source: README.md at commit faed420

Tools

5

list_apis

List monitored APIs

List 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.

Parameterscategory

get_api_status

Get current API status

Check 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?'.

Parametersapirequired

check_apis

Check several APIs at once

Check 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.

Parametersapisrequired

get_api_uptime

Get API uptime history

Get 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?'.

Parametersapirequired

list_recent_incidents

List recent API outages

List 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.

Parameterslimitcategory

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts