Skip to content

Go-Live Check MCP server

com.dontdeployonfriday/golive-checkdontdeployonfriday.comstreamable-httpv0.1.0Scanned

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

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Go-Live Check MCP server can do

The Go-Live Check MCP server is published by dontdeployonfriday.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: report_feedback), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (analyze_headers).

The fixed checks matched 4 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Claude Code: ask
  • report_feedbackReport one finding id and one outcome.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.id.enum[6] mentions "CREDENTIALS".

      Matched text

      inputSchema.properties.id.enum[6]: "GLC-CORS-WILDCARD-CREDENTIALS"

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Report a finding outcome
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • analyze_headersCheck raw HTTP response headers from a deployment you already operate.Reads text others write1 finding

    Why it is in this group

    • The name "analyze_headers" says "analyze": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.

    Findings

    • Info

      The input schema at properties.config_text.description mentions "CREDENTIALS".

      Matched text

      inputSchema.properties.config_text.description: "...e deletion is absent. GLC-CORS-WILDCARD-CREDENTIALS includes config_header present or absen..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Analyze response headers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • explain_findingExplain one finding id from the seven.1 finding

    Why it is in this group

    • The name "explain_finding" says "explain": a word for reading.

    Findings

    • Info

      The input schema at properties.id.enum[6] mentions "CREDENTIALS".

      Matched text

      inputSchema.properties.id.enum[6]: "GLC-CORS-WILDCARD-CREDENTIALS"

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain a finding
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_fixReturn the registry snippet for one finding id and one platform.1 finding

    Why it is in this group

    • The name "get_fix" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.id.enum[6] mentions "CREDENTIALS".

      Matched text

      inputSchema.properties.id.enum[6]: "GLC-CORS-WILDCARD-CREDENTIALS"

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a fix snippet
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://dontdeployonfriday.com/mcp: tools/list returned 4 tools to an anonymous client, including report_feedback (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

4 info
  • The input schema at properties.config_text.description mentions "CREDENTIALS".

    Matched text

    inputSchema.properties.config_text.description: "...e deletion is absent. GLC-CORS-WILDCARD-CREDENTIALS includes config_header present or absen..."

    What this check looks for
  • The input schema at properties.id.enum[6] mentions "CREDENTIALS".

    Matched text

    inputSchema.properties.id.enum[6]: "GLC-CORS-WILDCARD-CREDENTIALS"

    What this check looks for
  • The input schema at properties.id.enum[6] mentions "CREDENTIALS".

    Matched text

    inputSchema.properties.id.enum[6]: "GLC-CORS-WILDCARD-CREDENTIALS"

    What this check looks for
  • The input schema at properties.id.enum[6] mentions "CREDENTIALS".

    Matched text

    inputSchema.properties.id.enum[6]: "GLC-CORS-WILDCARD-CREDENTIALS"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__golive-check__analyze_headers",
      "mcp__golive-check__explain_finding",
      "mcp__golive-check__get_fix"
    ],
    "ask": [
      "mcp__golive-check__report_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as golive-check. Review it before you use it.

Capability tags behind 1 rule
  • mcp__golive-check__analyze_headers untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.dontdeployonfriday/golive-check/verify?hash=b851760ca165bc02b9406a3efc7c62f7c597339e7fc34fd294a61a95cc3b0946" | jq -e '.changed == false'

Pinned hash b851760ca165, from Nov 13, 2026, 02:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.dontdeployonfriday/golive-check/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.dontdeployonfriday/golive-check
[![Anlyon Radar](https://radar.anlyon.com/badge/com.dontdeployonfriday/golive-check.svg)](https://radar.anlyon.com/servers/com.dontdeployonfriday/golive-check)

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

Go-Live Check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Go-Live Check MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Go-Live Check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Go-Live Check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Go-Live Check MCP server have?

4 tools: 1 write, 3 read. report_feedback, analyze_headers, explain_finding and get_fix.

Does the Go-Live Check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Go-Live Check MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Go-Live Check MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.