Apizone

What apizone MCP server does

The apizone MCP server exposes APIzone's monitoring service through five read-only MCP tools. Agents can inspect the catalog of monitored services, query one service's current state, check multiple dependencies together, review historical uptime and latency, and list recent incidents. The monitored catalog includes 294 popular APIs such as Stripe, OpenAI, AWS, GitHub, and Twilio.

This is useful during troubleshooting and dependency checks. An agent can compare several upstream services in one request, determine whether a named API is currently up, degraded, or down, and review whether a service has experienced recent outages. The results describe observations made by APIzone's infrastructure and may not match an official provider status page.

How it works

APIzone runs synthetic checks against public, unauthenticated endpoints for monitored services. An HTTP response below 500 is treated as healthy, including authentication responses such as a 401 when that response demonstrates that the API is reachable. Timeouts, network failures, and 5xx responses count as failed checks.

Current state is derived from recent results. A service is considered down when its recent checks are consistently failing. Degraded status can indicate intermittent failures or latency substantially above the service's own baseline. APIzone performs an additional probe before opening an incident, which suppresses incidents caused by a transient failure that immediately clears.

The apizone MCP server is hosted and stateless. Clients connect to https://apizone.io/api/mcp using Streamable HTTP, so the repository does not need to be built or installed for normal use.

Setup and configuration

Add the hosted endpoint to an MCP client that supports Streamable HTTP. For Claude, the documented command is:

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

No API key, authentication, environment variables, local process, or build step is required. The repository includes a server.json registry manifest, while the running monitoring service is hosted by APIzone.

Tools and capabilities

The apizone MCP server provides these read-only tools:

• list_apis returns monitored APIs and their current status, with optional category filtering.
• get_api_status checks whether one API is up, degraded, or down now.
• check_apis checks several APIs together to help identify a failing dependency.
• get_api_uptime reports uptime percentages and p50/p95 latency for 24-hour, 7-day, 30-day, or 90-day periods.
• list_recent_incidents lists recent outages and degradations from newest to oldest.

APIzone also publishes a public JSON API without an API key, limited to 60 requests per minute per IP. That API includes current status, per-service history, uptime, latency, and incident data, but it is separate from the MCP connection.

Limitations and notes

The monitoring checks use public unauthenticated endpoints, so they represent externally observed availability rather than every aspect of a provider's service. A provider's official status page may show a different result. All MCP tools are read-only and require no authentication. The repository's MIT license covers its public documentation and registry manifest; the hosted APIzone service is proprietary.