Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Is It Down API (60SecMonitor)

REMOTE · API.ISITDOWNAPI.COM

Is this vendor down? Pay-per-call status for 1,400+ SaaS/cloud vendors, up to 25 per call (x402).

+3 this week 78 Trust /100

Last scanned (21 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 609 tokens (~121/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://api.isitdownapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=isitdownapi.com CN=WE1,O=Google Trust Services,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA256 bd90773c2cebfdc71377b69afc22cbb5
SANs: isitdownapi.com, api.isitdownapi.com, *.api.isitdownapi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.isitdownapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
isitdownapi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.isitdownapi.com/mcp Verified 200
http (plaintext) http://api.isitdownapi.com/mcp Inconclusive 405
MCP tools · 5 exposed · ~527 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_vendors ~102

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.

NameTypeReqDescription
pageinteger–Page number, starting at 1 (default 1)
searchstring–Optional name or slug filter, e.g. 'stripe' or 'aws'

No output schema declared.

No examples provided.

multi_vendor_status ~138

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 a single vendor. Untracked names are reported, not fatal. Not charged if none of the vendors is tracked or every lookup fails. Read-only; one flat price of $0.05 USDC via x402 (payment goes in _meta["x402/payment"]).

NameTypeReqDescription
vendorsarrayyes1-25 vendor names, slugs or domains

No output schema declared.

No examples provided.

pricing ~41

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_vendor ~81

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.

NameTypeReqDescription
vendorstringyesVendor name, slug or domain, e.g. 'Stripe', 'stripe' or stripe.com

No output schema declared.

No examples provided.

vendor_status ~165

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 up to 25 vendors at a flat price. Call list_vendors (free) first if you are not sure the vendor is tracked: unknown vendors return an error and are not charged. Read-only. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure is not charged.

NameTypeReqDescription
vendorstringyesVendor name, slug or domain, e.g. 'Stripe', 'stripe' or stripe.com

No output schema declared.

No examples provided.

Install

How do I install the Is It Down API (60SecMonitor) MCP server?

Is It Down API (60SecMonitor) is a hosted endpoint at https://api.isitdownapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.isitdownapi.com

# add to Claude Code
claude mcp add --transport http com-isitdownapi-api-status 'https://api.isitdownapi.com/mcp'
Common questions

What is the Is It Down API (60SecMonitor) MCP server?

Is It Down API (60SecMonitor) is an MCP server listed in the public MCP registry as com.isitdownapi.api/status. Is this vendor down? Pay-per-call status for 1,400+ SaaS/cloud vendors, up to 25 per call (x402). This page covers its hosted endpoint (https://api.isitdownapi.com/mcp).

Is the Is It Down API (60SecMonitor) MCP server safe to use?

Is It Down API (60SecMonitor) scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Is It Down API (60SecMonitor) MCP server expose?

Is It Down API (60SecMonitor) exposes 5 tools: list_vendors, validate_vendor, pricing, vendor_status, multi_vendor_status. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.

Does the Is It Down API (60SecMonitor) MCP server require authentication?

No. We connected to Is It Down API (60SecMonitor) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Is It Down API (60SecMonitor) MCP server still maintained?

Is It Down API (60SecMonitor) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.