Go-Live Check
REMOTE · DONTDEPLOYONFRIDAY.COM
Checks HTTP response headers you paste: 7 security checks with copy-paste fixes. No fetching.
Available components
Last scanned (11 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +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.
- 20 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://dontdeployonfriday.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dontdeployonfriday.com | CN=YE1,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 63caa057884729f0bbbc71931e8085b11c8 |
| SANs: dontdeployonfriday.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dontdeployonfriday.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dontdeployonfriday.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self' https://eu-assets.i.posthog.com; connect-src 'self' https://eu.i.posthog.com https://eu-assets.i.posthog.com; worker-src 'self' blob: data:; style-src 'self'; img-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dontdeployonfriday.com/mcp | Verified | 200 | |
| http (plaintext) | http://dontdeployonfriday.com/mcp | HTTPS enforced | 308 | https://dontdeployonfriday.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_headers ~1,006
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| checked | array | yes | – |
| config_text | – | yes | – |
| findings | array | yes | – |
| notes | array | yes | – |
| parsed_header_count | integer | yes | – |
| paths_tested_count | integer | yes | – |
| platform | – | yes | – |
| schema | – | yes | – |
No examples provided.
explain_finding ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | One finding id from the seven. Unknown fields are ignored. A url field is not fetched. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer_page | – | yes | 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 | yes | – |
| severity | string | yes | – |
| why | string | yes | – |
No examples provided.
get_fix ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| fix | – | yes | – |
| id | string | yes | – |
No examples provided.
report_feedback ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | One finding id from the seven. A note, a url, and headers are ignored. A url field is not fetched. |
| outcome | string | yes | Exactly one of false_positive, fix_worked, fix_failed. Any other value is unknown_outcome. Nothing is written. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| outcome | string | yes | – |
| stored | – | yes | – |
No examples provided.
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.
remote · dontdeployonfriday.com
claude mcp add --transport http com-dontdeployonfriday-golive-check 'https://dontdeployonfriday.com/mcp'
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.