Tariff Code Compliance for Claude

Tariff Code Compliance gives Claude one guided workflow for researching a product against current tariff data. It combines the existing read-only Tariff Code Compliance connector with the canonical classify-product skill, so a user can install once and ask for a classification without knowing MCP tool names or installing a separate skill.

What the plugin includes

• classify-product: gathers only decision-relevant product facts, discovers the current tariff system and exact active version, researches graph evidence, compares realistic alternatives, and explains uncertainty.
• tariff-code-compliance: the existing production Streamable HTTP connector at https://api.prod.tariffcodecompliance.com/tariff-code-compliance/v1/mcp.

The plugin adds no local server, executable code, hooks, sub-agents, monitors, or write-capable tools.

Install and use

After the plugin is published, eligible Claude users install Tariff Code Compliance once from Customize > Plugins. Claude makes the classification skill available in web and Desktop Chat and in Cowork. The connector remains on demand: when the workflow first needs tariff evidence, Claude asks the user to connect or sign in through Tariff Code Compliance OAuth.

Start with a normal request. Claude can select the skill automatically when the intent is clear, or the user can select classify-product from the skills menu.

Examples:

1. Classify a men's knitted cotton T-shirt for import into the United States.
2. Research the U.S. tariff classification for a 20,000 mAh lithium-ion power bank. Ask me only for missing facts that could change the code.
3. I import a stainless-steel vacuum bottle into the United States. Find the current HTS classification, show the evidence and rejected alternatives, and explain what remains uncertain.

The result includes the selected tariff system and exact version, recommended code and description, product facts used, supporting evidence, rejected alternatives, assumptions, and uncertainty. Codes, legal notes, terms, and annotations appear as readable links to the same exact version in Tariff Code Explorer; internal graph IDs and continuation tokens stay out of the customer answer. If the evidence or product facts are insufficient, Claude returns focused questions and unresolved candidates instead of forcing a code.

Trust and data boundaries

• Tariff Code Compliance tools read tariff evidence. They do not file customs entries, update a catalog, create a binding ruling, or write to another product.
• A recommendation is non-binding research support, not legal advice or a binding customs determination. The user controls downstream use.
• Keep classification responses focused on classification. Duty rates, fees, taxes, landed cost, and calculations belong in a separate workflow.
• Send only the product, destination, and classification facts required for the research. Do not send personal information, credentials, authentication secrets, or unrelated data.

Connector identity and lazy loading

The bundled MCP entry uses the exact URL of the published Tariff Code Compliance directory connector. Claude should match and reuse that connector when it is already connected instead of presenting a second TCC tool surface. Tool schemas remain deferred until Claude needs them.

Source and support

The plugin source distributed through Claude is available at glasswavesco/tariff-code-compliance-claude-plugin.

For product documentation, visit the Tariff Code Compliance agent guide. For questions or security concerns, contact Tariff Code Compliance support.

License

This plugin is proprietary Glasswaves software. Use is governed by the Tariff Code Compliance Terms of Service.