# Zovo Website Status Checker (remote · site-status.zovo.one)

Is it down, or just you?

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `site-status.zovo.one`: 75/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-site-status/site-status.md), [page](https://verifymcp.io/servers/theluckystrike-site-status/site-status)

## Channel facts

- Endpoint: `https://site-status.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 494 tokens (~164/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Website Status Checker MCP server?

Zovo Website Status Checker is a hosted endpoint at https://site-status.zovo.one/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.

### Claude

```bash
claude mcp add --transport http theluckystrike-site-status 'https://site-status.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-site-status": {
      "url": "https://site-status.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-site-status": {
      "type": "http",
      "url": "https://site-status.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-site-status]
url = "https://site-status.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-site-status": {
      "type": "remote",
      "url": "https://site-status.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-site-status --url 'https://site-status.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-site-status:
    url: "https://site-status.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-site-status": {
      "Transport": "http",
      "Url": "https://site-status.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-site-status -t streamable-http -u 'https://site-status.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-site-status": {
      "type": "http",
      "url": "https://site-status.zovo.one/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 74)

First indexed and scored.

## MCP tools (2)

### `check_websites` (~186 tokens)

Check websites

Use this when the user asks "is it down", "is this website down", "website down checker", "check if site is up", or "website status" for one or more domains: it makes a live request from the edge network and reports the verdict, redirect chain, HTTP status, response time, TLS, page title and security headers for up to 10 URLs, plus a CSV download. It cannot check IP literals, private or reserved addresses, or ports other than 80 and 443, and a site can block the check. Do not use for monitoring, uptime history, or checking an internal or private address.

Input parameters:

- `urls` (array, required): The websites to check, 1 to 10. Each entry is a domain such as example.com or a full http(s) address, e.g. ["example.com", "https://www.cloudflare.com"].

Output parameters:

- `checked_at` (string)
- `down_count` (number)
- `downloads` (object)
- `results` (array)
- `source` (object)
- `summary` (string)
- `up_count` (number)

### `check_security_headers` (~178 tokens)

Check security headers

Use this when the user asks for a "security headers check", "http status checker", or "website status" or wants to know which HTTPS and security headers a website sends: it makes one live request from the edge network and reports the six key headers (Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options or frame-ancestors, Referrer-Policy, Permissions-Policy) with an A-F grade, plus TLS, robots.txt and a CSV download. It checks one address at a time, cannot check private or reserved addresses, and does not scan the page content. Do not use for vulnerability tests or checks of more than one site.

Input parameters:

- `url` (string, required): One website to check the security headers and HTTPS for, e.g. https://example.com.

Output parameters:

- `downloads` (object)
- `final_url` (string)
- `grade` (string)
- `grade_score` (number)
- `headers` (array)
- `headers_missing` (array)
- `headers_present` (array)
- `source` (object)
- `state` (string)
- `status` (number|null)
- `status_text` (string)
- `tls` (boolean)
- `total_ms` (number)
- `url` (string)
- `verdict` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-site-status/site-status#diagnostics

## Score history

- 2026-10-23: 75
- 2026-10-22: 74

## Common questions

### What is the Zovo Website Status Checker MCP server?

Zovo Website Status Checker is an MCP server listed in the public MCP registry as io.github.theluckystrike/site-status. Is it down, or just you? This page covers its hosted endpoint (https://site-status.zovo.one/mcp).

### Is the Zovo Website Status Checker MCP server safe to use?

Zovo Website Status Checker scores 75 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 Zovo Website Status Checker MCP server expose?

Zovo Website Status Checker exposes 2 tools: check_websites, check_security_headers. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.

### Does the Zovo Website Status Checker MCP server require authentication?

No. We connected to Zovo Website Status Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Website Status Checker MCP server still maintained?

Zovo Website Status Checker is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://site-status.zovo.one/mcp
- Website: https://site-status.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-site-status/site-status.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-site-status/site-status.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-site-status/site-status