fix_and_verify — 72hours security check MCP Prompt
fix_and_verify
is one of 2 prompts on the
72hours security check
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke fix_and_verify from your client
- Claude Code 72hours security check Prompt/fix_and_verify run in your project directory
- Claude Desktop 72hours security check Prompt/fix_and_verify ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor 72hours security check Prompt/fix_and_verify ~/.cursor/mcp.json
- VS Code 72hours security check Prompt/fix_and_verify .vscode/mcp.json
- Zed 72hours security check Prompt/fix_and_verify ~/.config/zed/settings.json
- Windsurf 72hours security check Prompt/fix_and_verify ~/.codeium/windsurf/mcp_config.json
- Cline 72hours security check Prompt/fix_and_verify ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI 72hours security check Prompt/fix_and_verify ~/.gemini/settings.json
- Grok 72hours security check Prompt/fix_and_verify .mcp.json (in your project root)
- ChatGPT 72hours security check Prompt/fix_and_verify Settings → Connectors → Advanced → Developer mode
- Claude.ai 72hours security check Prompt/fix_and_verify Settings → Connectors → Add custom connector
- LangChain 72hours security check Prompt/fix_and_verify pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 11 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.