# Go-Live Check (remote · dontdeployonfriday.com)

Checks HTTP response headers you paste: 7 security checks with copy-paste fixes. No fetching.

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

## Components

- remote · `dontdeployonfriday.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-dontdeployonfriday-golive-check/dontdeployonfriday.md), [page](https://verifymcp.io/servers/com-dontdeployonfriday-golive-check/dontdeployonfriday)

## Channel facts

- Endpoint: `https://dontdeployonfriday.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2086 tokens (~521/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Go-Live Check MCP server?

Go-Live Check is a hosted endpoint at https://dontdeployonfriday.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.

### Claude

```bash
claude mcp add --transport http com-dontdeployonfriday-golive-check 'https://dontdeployonfriday.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dontdeployonfriday-golive-check": {
      "url": "https://dontdeployonfriday.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dontdeployonfriday-golive-check": {
      "type": "http",
      "url": "https://dontdeployonfriday.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-dontdeployonfriday-golive-check]
url = "https://dontdeployonfriday.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dontdeployonfriday-golive-check": {
      "type": "remote",
      "url": "https://dontdeployonfriday.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dontdeployonfriday-golive-check --url 'https://dontdeployonfriday.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dontdeployonfriday-golive-check:
    url: "https://dontdeployonfriday.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dontdeployonfriday-golive-check": {
      "Transport": "http",
      "Url": "https://dontdeployonfriday.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dontdeployonfriday-golive-check -t streamable-http -u 'https://dontdeployonfriday.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-dontdeployonfriday-golive-check": {
      "type": "http",
      "url": "https://dontdeployonfriday.com/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-22 (score 70, +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-10-20 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-19 (score 68)

First indexed and scored.

## MCP tools (4)

### `analyze_headers` (~1006 tokens)

Check raw HTTP response headers from a deployment you already operate. Returns the same object as POST /v1/analyze. Unknown fields are ignored. A url field is not fetched. Nothing is stored. Nothing is for sale.

Input parameters:

- `config_text` (string): Optional config text. Not copied into the response. When platform is caddy and this is non-empty, GLC-HSTS-MISSING includes config_header present or absent for one Caddy Strict-Transport-Security for…
- `headers_raw` (string, required): Raw HTTP response headers from a deployment this agent already operates, including an optional status line, as curl -sI prints them. This server does not request a URL.
- `paths_tested` (array): Optional paths. Accepted and not checked. This server does not request them.
- `platform` (string): Platform whose config the caller can edit. A fix snippet is attached only for caddy, nginx, vercel, netlify, or nextjs. Any other declared platform, or an omitted platform, returns fix null. This ser…

Output parameters:

- `checked` (array)
- `config_text`
- `findings` (array)
- `notes` (array)
- `parsed_header_count` (integer)
- `paths_tested_count` (integer)
- `platform`
- `schema`

### `explain_finding` (~107 tokens)

Explain one finding id from the seven. Returns id, severity, why, and answer_page. answer_page is the CSP and clickjacking page for GLC-CSP-MISSING and GLC-FRAME-MISSING, and null for the other five. Unknown fields are ignored. A url field is not fetched. Nothing is stored. Nothing is for sale.

Input parameters:

- `id` (string, required): One finding id from the seven. Unknown fields are ignored. A url field is not fetched.

Output parameters:

- `answer_page`: https://dontdeployonfriday.com/csp-and-clickjacking.html for GLC-CSP-MISSING and GLC-FRAME-MISSING. Null for the other five. This server does not fetch it.
- `id` (string)
- `severity` (string)
- `why` (string)

### `get_fix` (~194 tokens)

Return the registry snippet for one finding id and one platform. The platforms are caddy, nginx, vercel, netlify, nextjs. The result is id and fix. fix has platform, snippet, source_url, and last_verified, and note when the registry file has one. An omitted or unknown platform returns fix null. Unknown fields are ignored. A url field is not fetched. source_url is not fetched. Nothing is stored. Nothing is for sale.

Input parameters:

- `id` (string, required): One finding id from the seven. Unknown fields are ignored. A url field is not fetched.
- `platform` (string): Platform whose config the caller can edit. caddy, nginx, vercel, netlify, nextjs returns that registry snippet. Any other value, or an omitted platform, returns fix null. This server does not guess t…

Output parameters:

- `fix`
- `id` (string)

### `report_feedback` (~152 tokens)

Report one finding id and one outcome. The outcomes are false_positive, fix_worked, fix_failed. The result is id, outcome, and stored false. Nothing is written: no file, no counter, and no log line. A note, a url, and headers are ignored. A url field is not fetched. This server does not guess the platform from the Server header. Nothing is for sale.

Input parameters:

- `id` (string, required): One finding id from the seven. A note, a url, and headers are ignored. A url field is not fetched.
- `outcome` (string, required): Exactly one of false_positive, fix_worked, fix_failed. Any other value is unknown_outcome. Nothing is written.

Output parameters:

- `id` (string)
- `outcome` (string)
- `stored`

## Diagnostics

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

## Score history

- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68

## Common questions

### What is the Go-Live Check MCP server?

Go-Live Check is an MCP server listed in the public MCP registry as com.dontdeployonfriday/golive-check. Checks HTTP response headers you paste: 7 security checks with copy-paste fixes. No fetching. This page covers its hosted endpoint (https://dontdeployonfriday.com/mcp).

### Is the Go-Live Check MCP server safe to use?

Go-Live Check scores 70 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 Go-Live Check MCP server expose?

Go-Live Check exposes 4 tools: analyze_headers, explain_finding, get_fix, report_feedback. Their descriptions and schemas cost roughly 1,459 tokens of context every time the server is loaded.

### Does the Go-Live Check MCP server require authentication?

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

### Is the Go-Live Check MCP server still maintained?

Go-Live Check 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://dontdeployonfriday.com/mcp
- Website: https://dontdeployonfriday.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dontdeployonfriday-golive-check/dontdeployonfriday.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dontdeployonfriday-golive-check/dontdeployonfriday.json
- HTML version of this page: https://verifymcp.io/servers/com-dontdeployonfriday-golive-check/dontdeployonfriday