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 This Site Down?

REMOTE · DOWNFORJUSTMEOREVERYONE.COM · SCANNED OCT 7

Check if any website is down, from two continents, with uptime history and TLS expiry

+4 this week 78 Trust /100
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 Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 634 tokens (~126/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 Management83
  • Stability observed for 25 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Is This Site Down? MCP server?

Is This Site Down? is a hosted endpoint at https://downforjustmeoreveryone.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 · downforjustmeoreveryone.com

# add to Claude Code
claude mcp add --transport http com-downforjustmeoreveryone-is-it-down 'https://downforjustmeoreveryone.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-downforjustmeoreveryone-is-it-down": {
      "url": "https://downforjustmeoreveryone.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-downforjustmeoreveryone-is-it-down": {
      "type": "http",
      "url": "https://downforjustmeoreveryone.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-downforjustmeoreveryone-is-it-down]
url = "https://downforjustmeoreveryone.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-downforjustmeoreveryone-is-it-down": {
      "type": "remote",
      "url": "https://downforjustmeoreveryone.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-downforjustmeoreveryone-is-it-down --url 'https://downforjustmeoreveryone.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-downforjustmeoreveryone-is-it-down:
    url: "https://downforjustmeoreveryone.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-downforjustmeoreveryone-is-it-down": {
      "Transport": "http",
      "Url": "https://downforjustmeoreveryone.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-downforjustmeoreveryone-is-it-down -t streamable-http -u 'https://downforjustmeoreveryone.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-downforjustmeoreveryone-is-it-down": {
      "type": "http",
      "url": "https://downforjustmeoreveryone.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 7 Oct 26 +1

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

  • 5 Oct 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.

  • 3 Oct 26 +1

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

  • 1 Oct 26 +1

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

  • 29 Sept 26 +1

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

  • 28 Sept 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 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.

  • 25 Sept 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 7 Oct 2026 · Probed https://downforjustmeoreveryone.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=downforjustmeoreveryone.com CN=YE1,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA384 51cfdcfb215ce722fc08a83794490db99c5
SANs: *.downforjustmeoreveryone.com, downforjustmeoreveryone.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of downforjustmeoreveryone.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
downforjustmeoreveryone.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://downforjustmeoreveryone.com/mcp Verified 200
http (plaintext) http://downforjustmeoreveryone.com/mcp Inconclusive 302 /api#mcp
MCP tools · 5 exposed · ~499 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
check_certificate ~46

Reads the HTTPS certificate of a public domain and reports days until expiry, the expiry date and the issuer.

NameTypeReqDescription
domainstringyesDomain to inspect, e.g. "example.com".
NameTypeReqDescription
daysRemainingnumberyesNegative once expired
domainstringyes–
issuerstring|nullyes–
statestringyes–
validTostringyes–

No examples provided.

check_site ~125

Live up/down check of any public website from an independent server (Singapore; Boston for sites that geo-block Singapore). Returns a one-sentence verdict plus status code, latency, resolved IP, redirect target, the view from the other region when available, and how many users reported problems in the last hour. Results are cached 30 s per domain.

NameTypeReqDescription
domainstringyesDomain or URL to check, e.g. "github.com" or "https://www.reddit.com/r/all". Scheme, path, port and query are ignored; the host is checked as given.
NameTypeReqDescription
checkedAtstringyesISO 8601
checkedFromstringyessg = Singapore, us = Boston
curatedbooleanyestrue if the site is one of the monitored sites
domainstringyes–
finalUrlstring|null––
ipstring|null––
latencyMsnumber|nullyes–
reasonstringyes–
redirectedboolean––
regionsobjectyesFresh result from each region that has one
reportsLastHourintegeryes–
schemestring|null––
serverstring|null––
statestringyes–
statusinteger|nullyes–
statusUrlstring|nullyes–
tlsobject|null––
upbooleanyes–
urlstringyes–

No examples provided.

list_monitored_sites ~125

The 634 sites checked every 5 minutes, grouped in 17 categories. Without arguments returns the category list with counts; filter by category or a text query to get domains (at most 200 per call).

NameTypeReqDescription
categorystring–Category slug or name: social, streaming, ai, work, developer, shopping, finance, banks, gaming, telecom, government, education, messaging, news, travel, health, dating.
querystring–Case-insensitive substring of the domain or display name, e.g. "bank" or "google".
NameTypeReqDescription
categoriesarray––
categorystring|null––
matchedinteger––
querystring|null––
returnedinteger––
sitesarray––
totalintegeryes–

No examples provided.

list_outages ~99

Lists the monitored sites (634 across 17 categories) that are confirmed down right now: two consecutive failed checks from their home region and no other region seeing them up in the last 15 minutes. Optional category filter.

NameTypeReqDescription
categorystring–Optional category slug or name: social, streaming, ai, work, developer, shopping, finance, banks, gaming, telecom, government, education, messaging, news, travel, health, dating.
NameTypeReqDescription
asOfstringyes–
categorystring|nullyes–
downarrayyes–
monitoredintegeryes–

No examples provided.

site_history ~104

Uptime percentage over 24 h and over the requested window (up to 7 days), the list of outages in that window, when the site was last seen down, the current state and user-report counts. Only for monitored sites (see list_monitored_sites); use check_site for anything else.

NameTypeReqDescription
daysinteger–Window in days (1–7, default 7).
domainstringyesA monitored domain, e.g. "github.com".
NameTypeReqDescription
categorystringyes–
checkedFromstringyessg = Singapore, us = Boston
currentobject|nullyes–
daysintegeryes–
domainstringyes–
incidentsarrayyes–
lastDownstring|nullyes–
namestringyes–
reports24hintegeryes–
reportsLastHourintegeryes–
statusUrlstring|nullyes–
uptime24hnumber|nullyesPercent, null if no data yet
uptimeWindownumber|nullyesPercent over `days`, null if no data yet
urlstringyes–

No examples provided.

Common questions

What is the Is This Site Down? MCP server?

Is This Site Down? is an MCP server listed in the public MCP registry as com.downforjustmeoreveryone/is-it-down. Check if any website is down, from two continents, with uptime history and TLS expiry. This page covers its hosted endpoint (https://downforjustmeoreveryone.com/mcp).

Is the Is This Site Down? MCP server safe to use?

Is This Site Down? 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 This Site Down? MCP server expose?

Is This Site Down? exposes 5 tools: check_site, list_outages, site_history, check_certificate, list_monitored_sites. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.

Does the Is This Site Down? MCP server require authentication?

No. We connected to Is This Site Down? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Is This Site Down? MCP server still maintained?

Is This Site Down? is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.