Skip to content
60SecMonitor logo

60SecMonitor MCP server

Which MCP servers are 60SecMonitor's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to 60SecMonitor

Whose server it is
  • Registry namecom.isitdownapi.api/statusverified in the MCP registry

The registry name sits under isitdownapi.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools5
  • Server calls itselfisitdownapi-status
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 194 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer218 ms
  • Space in an agent's context≈ 758 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-27
  • list_vendors

    Free. List or search the vendors 60SecMonitor tracks (slug, name, category), paged. Use it before paying to confirm a vendor is tracked and to get its exact slug. Read-only; one request to 60SecMonitor, no payment.

  • validate_vendor

    Free. Check that a vendor name, slug or domain is well-formed and see how it will be matched. Format only and offline (no network request, no payment); use list_vendors to confirm the vendor is actually tracked.

  • pricing

    Free. Return the price of every paid tool, the payment network (Base), the receiving address and the data source. No input, no network request, no payment.

  • vendor_status

    Check whether one SaaS or cloud vendor (e.g. Stripe) is down right now: current status, confidence, active incidents, 30-day uptime and how fresh the data is, read live from 60SecMonitor. Use it for one vendor; use multi_vendor_status for…

  • multi_vendor_status

    Check the status of up to 25 SaaS or cloud vendors in one call, for "is my stack down?" questions: per-vendor status and a list of the ones not operational, read live from 60SecMonitor. Use vendor_status when you need incident detail for…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "status": {
      "type": "http",
      "url": "https://api.isitdownapi.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http isitdownapi https://api.isitdownapi.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.isitdownapi.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.