# Corrie Site Check (remote · corrie.io)

Free HTTPS and security header check from Corrie, uptime monitoring for small teams. No auth.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `corrie.io`: 83/100 (this document), [markdown](https://verifymcp.io/servers/io-corrie-site-check/corrie.md), [page](https://verifymcp.io/servers/io-corrie-site-check/corrie)

## Channel facts

- Endpoint: `https://corrie.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-05.

- **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. 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 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**: 77/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 589 tokens (~196/item across 3 items; 1 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Corrie Site Check MCP server?

Corrie Site Check is a hosted endpoint at https://corrie.io/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 io-corrie-site-check 'https://corrie.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-corrie-site-check": {
      "url": "https://corrie.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-corrie-site-check": {
      "type": "http",
      "url": "https://corrie.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-corrie-site-check]
url = "https://corrie.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-corrie-site-check": {
      "type": "remote",
      "url": "https://corrie.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-corrie-site-check --url 'https://corrie.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-corrie-site-check:
    url: "https://corrie.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-corrie-site-check": {
      "Transport": "http",
      "Url": "https://corrie.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-corrie-site-check -t streamable-http -u 'https://corrie.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-corrie-site-check": {
      "type": "http",
      "url": "https://corrie.io/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-05 (score 83, +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.

### 2026-11-02 (score 82, +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.

### 2026-10-31 (score 81, +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.

### 2026-10-29 (score 80, +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.

### 2026-10-27 (score 79, +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.

### 2026-10-26 (score 78, 0)

- [functional] Server version: 1.1.0 → 1.1.1

### 2026-10-25 (score 78, +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.

### 2026-10-23 (score 77, +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.

## MCP tools (1)

### `check_website` (~396 tokens)

Check a website's HTTPS and security headers

Loads the homepage of one public website over HTTPS, the way a visitor's browser would, and reports its HTTPS setup, TLS certificate and security headers (Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, cookie flags, mixed content and server banners). Returns a score from 0 to 100, a verdict, the TLS certificate issuer and expiry date, and each finding with a severity (critical, high, medium or low) and a plain-English fix that includes nginx or Cloudflare examples. Use it for questions like 'is example.com secure?', 'what security headers is my site missing?', 'when does this site's certificate expire?' or 'why does Chrome say my site is not secure?'. Input is a bare domain (example.com) or an https:// address. A bare domain checks the homepage; if you include a path, that one page is loaded instead. It does not log in, submit forms, scan ports, crawl other pages or test for vulnerabilities, and nothing is stored. It refuses private, internal and local addresses, plain http://, ports other than 443 and addresses with a user name; those come back as an isError result with a message saying what to change. A check usually takes 1 to 10 seconds. Running it twice on the same site gives the same result unless the site changed. Read corrie://docs/scoring for how the score and verdict work.

Input parameters:

- `url` (string, required): The public website to check: a bare domain such as example.com, or an https:// address such as https://www.example.com/. If you leave out the scheme, https:// is added. Only port 443 is allowed. Priv…

Output parameters:

- `certificate` (object|null): Facts about the site's TLS certificate. Fields are null when not observed.
- `counts` (object): Number of findings at each severity.
- `final_url` (string): The address after following up to 3 redirects.
- `findings` (array): Problems found, most severe first. Empty when nothing was found.
- `http_status` (integer|null): HTTP status code of the final response.
- `limitations` (array): What this quick check does not cover.
- `report_url` (string): Where a person can run the same check in a browser.
- `score` (integer): Starts at 100. Each finding subtracts points: critical 35, high 15, medium 6, low 2. Never below 0.
- `url` (string): The normalized https:// address that was requested.
- `verdict` (string): One-line summary based on the most severe finding.

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 73

## Common questions

### What is the Corrie Site Check MCP server?

Corrie Site Check is an MCP server listed in the public MCP registry as io.corrie/site-check. Free HTTPS and security header check from Corrie, uptime monitoring for small teams. No auth. This page covers its hosted endpoint (https://corrie.io/mcp).

### Is the Corrie Site Check MCP server safe to use?

Corrie Site Check scores 83 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 Corrie Site Check MCP server expose?

Corrie Site Check exposes 1 tool: check_website. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.

### Does the Corrie Site Check MCP server require authentication?

No. We connected to Corrie Site Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Corrie Site Check MCP server still maintained?

Corrie Site Check is still listed as active in the MCP registry. We last reached this channel on 5 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 Corrie Site Check MCP server?

VerifyMCP ran 13 checks on Corrie Site Check, 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://corrie.io/mcp
- Website: https://corrie.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-corrie-site-check/corrie.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-corrie-site-check/corrie/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-corrie-site-check/corrie.json
- HTML version of this page: https://verifymcp.io/servers/io-corrie-site-check/corrie