vendor_trust_check — Trooth MCP Prompt

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

by client

How to invoke vendor_trust_check from your client

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

Other prompts on this server

• verify_trust_token
• before_you_trust

Trooth also offers 3 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.