Categories › Security › Code & dependency scanning
Checks HTTP response headers you paste: 7 security checks with copy-paste fixes. No fetching.
Remote server: your requests and data go to dontdeployonfriday.com. Claude Code: claude mcp add --transport http go-live-check https://dontdeployonfriday.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
analyze_headers — Check raw HTTP response headers from a deployment you already operate. Returns the same object as POST /v1/analyze. Unknown fields are ignorexplain_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-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 areport_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.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.