Skip to content

io.github.HappyMealSteak/apizone

by HappyMealSteak · remote · no sign-in to list tools · v1.0.1 · published by GitHub user HappyMealSteak

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

Changes · 1
CompareRegistry entry

5 tools: 1 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 1Claude Code: ask
  • check_apisCheck the current status of multiple APIs in one call — useful when diagnosing a failing app that depends on several services (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true
Only reads 4Claude Code: allow
  • get_api_statusCheck whether a specific API is currently up, degraded, or down.No findings

    Why it is in this group

    • The name "get_api_status" says "get": a word for reading.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true
  • get_api_uptimeGet uptime percentage and latency (median + 95th percentile) for an API over the last 24 hours, 7 days, 30 days, and 90 days.No findings

    Why it is in this group

    • The name "get_api_uptime" says "get": a word for reading.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true
  • list_apisList the APIs APIzone monitors and their current status (operational, degraded, down, or unknown).No findings

    Why it is in this group

    • The name "list_apis" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true
  • list_recent_incidentsList recent API outages and degradations detected by APIzone, newest first.No findings

    Why it is in this group

    • The name "list_recent_incidents" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__apizone__list_apis",
      "mcp__apizone__get_api_status",
      "mcp__apizone__get_api_uptime",
      "mcp__apizone__list_recent_incidents"
    ],
    "ask": [
      "mcp__apizone__check_apis"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as apizone. Review it before you use it.