verify_provenance — catalog MCP Prompt

verify_provenance is one of 3 prompts on the catalog MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke verify_provenance from your client

• Claude Code catalog Prompt/verify_provenance run in your project directory
• Claude Desktop catalog Prompt/verify_provenance ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor catalog Prompt/verify_provenance ~/.cursor/mcp.json
• VS Code catalog Prompt/verify_provenance .vscode/mcp.json
• Zed catalog Prompt/verify_provenance ~/.config/zed/settings.json
• Windsurf catalog Prompt/verify_provenance ~/.codeium/windsurf/mcp_config.json
• Cline catalog Prompt/verify_provenance ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI catalog Prompt/verify_provenance ~/.gemini/settings.json
• Grok catalog Prompt/verify_provenance .mcp.json (in your project root)
• ChatGPT catalog Prompt/verify_provenance Settings → Connectors → Advanced → Developer mode
• Claude.ai catalog Prompt/verify_provenance Settings → Connectors → Add custom connector
• LangChain catalog Prompt/verify_provenance pip install langchain-mcp-adapters

Other prompts on this server

• plan_build
• compare_for_project

catalog also offers 5 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 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.