Skip to content
Go-Live Check logo

Go-Live Check MCP server

Which MCP servers are Go-Live Check's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Go-Live Check

Whose server it is
  • Registry namecom.dontdeployonfriday/golive-checkverified in the MCP registry

The registry name sits under dontdeployonfriday.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools4
  • Server calls itselfgolive-check
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 499 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: find missing security headers in a deployment's HTTP responses; get fix snippets for Caddy, Nginx, Vercel, Netlify or Next.js.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "find missing security headers in a deployment's HTTP responses", the likely first call is analyze_headers.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer501 ms
  • Space in an agent's context≈ 1,908 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · find missing security headers in a deployment's HTTP responses
  • can do · get fix snippets for Caddy, Nginx, Vercel, Netlify or Next.js
  • not sure · flag CORS wildcard origins combined with credentials

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-28
  • analyze_headers

    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.

  • explain_finding

    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…

  • get_fix

    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…

  • report_feedback

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http dontdeployonfriday https://dontdeployonfriday.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://dontdeployonfriday.com/mcp as a custom connector in the settings.

OpenAPI spec

2 paths, read 2026-10-28. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.