How Trooth witnesses trust — Trooth MCP Resource

How Trooth witnesses trust is one of 3 resources on the Trooth MCP server. Connect the server and your client can attach it as context.

by client

How to attach How Trooth witnesses trust from your client

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

Other resources on this server

• Provenance labels, explained
• Agent pattern: check a vendor before relying on it

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