verification-policy — Second Opinion MCP Resource

verification-policy is one of 1 resource on the Second Opinion MCP server. Connect the server and your client can attach it as context.

by client

How to attach verification-policy from your client

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

Second Opinion also offers 2 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.