Provenance labels, explained — Trooth MCP Resource

Provenance labels, explained 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 Provenance labels, explained from your client

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

Other resources on this server

• How Trooth witnesses trust
• Agent pattern: verify before you trust

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 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.