# isup.tools — is it down? (remote · isup.tools)

Website status check: is a site down for everyone or just you? Shows HTTP code, time and location.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `isup.tools`: 77/100 (this document), [markdown](https://verifymcp.io/servers/tools-isup-isup/isup.md), [page](https://verifymcp.io/servers/tools-isup-isup/isup)

## Channel facts

- Endpoint: `https://isup.tools/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## 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-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 257 tokens (~257/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the isup.tools — is it down? MCP server?

isup.tools — is it down? is a hosted endpoint at https://isup.tools/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 tools-isup-isup 'https://isup.tools/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tools-isup-isup": {
      "url": "https://isup.tools/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tools-isup-isup": {
      "type": "http",
      "url": "https://isup.tools/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tools-isup-isup]
url = "https://isup.tools/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tools-isup-isup": {
      "type": "remote",
      "url": "https://isup.tools/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tools-isup-isup --url 'https://isup.tools/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tools-isup-isup:
    url: "https://isup.tools/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tools-isup-isup": {
      "Transport": "http",
      "Url": "https://isup.tools/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tools-isup-isup -t streamable-http -u 'https://isup.tools/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tools-isup-isup": {
      "type": "http",
      "url": "https://isup.tools/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-11-21 (score 77, +3)

- [security improvement] HSTS header: fail → pass

### 2026-11-20 (score 74, +1)

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

### 2026-11-18 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 72)

First indexed and scored.

## MCP tools (1)

### `check_site` (~138 tokens)

Check if a website is down

Check if a website is up or down right now. Use it when someone asks whether a site is down, or if it is just them. Makes one request to the site and returns a verdict sentence, the status (UP, DOWN or NOT CHECKABLE), the HTTP code, the time taken, and the real place the check ran from. The check runs near the machine that calls this tool, which may not be near the end user. The site's content is never read.

Input parameters:

- `url` (string, required): The domain or full URL to check, for example example.com or https://example.com/status. A bare domain is tried over https first.

Output parameters:

- `checkedAt` (string): When the check ran (UTC).
- `checkedFrom` (string): The real place the check ran from: a city, a raw location code when the city is not known, or "Location unavailable". Never guessed.
- `finalUrl` (string|null): The last URL requested, after any redirects, or null when no request was sent.
- `httpCode` (integer|null): HTTP status code of the last answer, or null when there was no answer.
- `latencyMs` (number|null): Time the whole check took, in milliseconds, or null when no request was sent (unsupported port).
- `reason` (string): One line on what happened.
- `redirects` (array): Every redirect answer, in order: the URL requested and the 3xx code it answered. Empty when there were no redirects. A redirect the safety rules refused is not listed (reason says it was not followed…
- `resultUrl` (string): HTML page for this target. Opening it runs a new check.
- `status` (string): UP: answered below HTTP 400. DOWN: answered 400 or higher (except 401, 403, 429), or no answer. NOT CHECKABLE: isup cannot reach this port or address (httpCode null), or the site answered 401, 403 or…
- `target` (string): The last URL checked, after any redirects.
- `verdict` (string): The verdict sentence, for example "It's just you. example.com is up."

## Diagnostics

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

## Score history

- 2026-11-21: 77
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72

## Common questions

### What is the isup.tools — is it down? MCP server?

isup.tools — is it down? is an MCP server listed in the public MCP registry as tools.isup/isup. Website status check: is a site down for everyone or just you? Shows HTTP code, time and location. This page covers its hosted endpoint (https://isup.tools/mcp).

### Is the isup.tools — is it down? MCP server safe to use?

isup.tools — is it down? scores 77 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 isup.tools — is it down? MCP server expose?

isup.tools — is it down? exposes 1 tool: check_site. Their descriptions and schemas cost roughly 138 tokens of context every time the server is loaded.

### Does the isup.tools — is it down? MCP server require authentication?

No. We connected to isup.tools — is it down? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the isup.tools — is it down? MCP server still maintained?

isup.tools — is it down? is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the isup.tools — is it down? MCP server?

VerifyMCP ran 13 checks on isup.tools — is it down?, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://isup.tools/mcp
- Website: https://isup.tools/
- Changelog RSS feed: https://verifymcp.io/servers/tools-isup-isup/isup.xml
- Changelog JSON feed: https://verifymcp.io/servers/tools-isup-isup/isup/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tools-isup-isup/isup.json
- HTML version of this page: https://verifymcp.io/servers/tools-isup-isup/isup
