investigate_origin — us tariff ledger MCP Prompt

investigate_origin is one of 4 prompts on the us tariff ledger MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke investigate_origin from your client

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

Other prompts on this server

• classify_and_cost
• check_before_you_cite
• monthly_briefing

us tariff ledger also offers 6 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.