_ registry / mcp http-sse · checked 46m ago

apizone

https://apizone.io

Registry code: a85abb3f225df9bb

api record

APIzone provides independent, real-time status monitoring for 294 popular APIs (Stripe, OpenAI, AWS, GitHub, Twilio, and more). Use these tools to check whether an API is currently down, look up uptime/reliability history, or list recent outages. Status reflects APIzone's own independent probes and may differ from a vendor's official status page.

endpoint
https://apizone.io/api/mcp
protocol
http-sse ·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 it live, free and safe measured by this hub
Is apizone live?
Yes — it answered the hub's last check (checked 46m ago). It answered 100% of checks over the last 30 days.
Is apizone free to use?
Yes — the hub reached it with no key and no payment.
What tools does apizone have?
5 tools: check_apis, get_api_status, get_api_uptime, list_apis, list_recent_incidents.
Is apizone 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.
reachable
live
uptime, 30 days
99.8%

90 days 99.8%· all time 99.8%

latency
259ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 583 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • check if an api is down
  • get api uptime history
  • list recent api outages
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

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_apis reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "category": {
          "enum": [
            "payments",
            "ai",
            "cloud",
            "developer-tools",
            "communication",
            "email",
            "auth",
            "analytics",
            "maps",
            "commerce",
            "social",
            "media",
            "data",
            "finance",
            "gaming",
            "productivity",
            "shipping",
            "web3"
          ],
          "type": "string",
          "description": "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"
        }
      }
    }
    arguments 30 lines
  • list_recent_incidents reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Max incidents to return (1-50)."
        },
        "category": {
          "enum": [
            "payments",
            "ai",
            "cloud",
            "developer-tools",
            "communication",
            "email",
            "auth",
            "analytics",
            "maps",
            "commerce",
            "social",
            "media",
            "data",
            "finance",
            "gaming",
            "productivity",
            "shipping",
            "web3"
          ],
          "type": "string",
          "description": "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"
        }
      }
    }
    arguments 37 lines
  • check_apis reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "apis"
      ],
      "properties": {
        "apis": {
          "type": "array",
          "items": {
            "type": "string",
            "minLength": 1
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "API names or slugs to check, e.g. ['stripe','openai','github']."
        }
      }
    }
    arguments 19 lines
  • get_api_status reads unknown 15h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "api"
      ],
      "properties": {
        "api": {
          "type": "string",
          "minLength": 1,
          "description": "API name or slug, e.g. 'stripe', 'OpenAI', 'github'."
        }
      }
    }
    arguments 14 lines
  • get_api_uptime reads unknown 7h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "api"
      ],
      "properties": {
        "api": {
          "type": "string",
          "minLength": 1,
          "description": "API name or slug, e.g. 'stripe', 'openai'."
        }
      }
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a85abb3f225df9bb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a85abb3f225df9bb/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a85abb3f225df9bb/badge.svg)](https://brick.blue/agent/a85abb3f225df9bb?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.

_ how we know
card completeness
90%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.