audit_and_seal — ProofCore MCP Prompt
audit_and_seal
is one of 1 prompt on the
ProofCore
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke audit_and_seal from your client
- Claude Code ProofCore Prompt/audit_and_seal run in your project directory
- Claude Desktop ProofCore Prompt/audit_and_seal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ProofCore Prompt/audit_and_seal ~/.cursor/mcp.json
- VS Code ProofCore Prompt/audit_and_seal .vscode/mcp.json
- Zed ProofCore Prompt/audit_and_seal ~/.config/zed/settings.json
- Windsurf ProofCore Prompt/audit_and_seal ~/.codeium/windsurf/mcp_config.json
- Cline ProofCore Prompt/audit_and_seal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ProofCore Prompt/audit_and_seal ~/.gemini/settings.json
- Grok ProofCore Prompt/audit_and_seal .mcp.json (in your project root)
- ChatGPT ProofCore Prompt/audit_and_seal Settings → Connectors → Advanced → Developer mode
- Claude.ai ProofCore Prompt/audit_and_seal Settings → Connectors → Add custom connector
- LangChain ProofCore Prompt/audit_and_seal pip install langchain-mcp-adapters
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.