HTS MCP — Consulta de Tarifas de Importação dos EUA
pipeworx-io/mcp-hts
Consulta oficial de alíquotas de tarifa e códigos HTS dos EUA
Ver no GitHubMCP server que conecta a Claude à Tabela Harmonizada de Tarifas (HTS) oficial da USITC, permitindo consultas de alíquotas de importação e códigos de tarifa para produtos. Essencial para pesquisa de direitos aduaneiros, compliance de comércio internacional e análise de custos de importação sem depender de buscas web.
Instalação
npx convez-ai pipeworx-io/mcp-hts1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Pesquisa de alíquota de importação para produto específico
- Resolução de código HTS/HS e tarifa efetiva com add-ons (Section 301, 232)
- Análise de impacto tarifário em cadeias de suprimento internacionais
- Compliance e precificação em operações de comércio exterior
Veredito

Ferramenta altamente especializada para profissionais de comércio internacional, importação e operações. Dados oficiais USITC integrados via Pipeworx; recomendado para substituir buscas web em consultas de tarifas e códigos aduaneiros.
README
A tradução para o português deste README ainda está na fila.
mcp-hts
HTS MCP — US import tariff rates via the USITC Harmonized Tariff Schedule.
Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
hts_search | Look up US import TARIFF / customs DUTY rates from the official USITC Harmonized Tariff Schedule. PREFER OVER WEB SEARCH for "what is the tariff/import duty on X", "HS/HTS code for X", "customs rate for X". Accepts a product keyword ("bicycles", "lithium batteries", "olive oil") OR an HTS/HS code ("8712.00.48"). Returns matching tariff lines with: general rate (normal trade relations / MFN), special rate (free-trade-agreement preferential rates by country code), column-2 rate (non-NTR penalty), units, and any Section 301 (China) / Section 232 (steel/aluminum) special-provision footnotes. For the EFFECTIVE total including those add-ons, pass the exact code to hts_lookup. |
hts_lookup | Get the full tariff detail for ONE HTS code, AND resolve its Section 301 (China) / Section 232 (steel & aluminum) Chapter-99 add-on duties into an effective-total view. Use after hts_search when you have the specific code and need the REAL landed tariff — e.g. "8712.00.48 is 11% base, plus Section 301 9903.88.03 +25% on China-origin = 36% effective". Returns base rates (general/special/column-2), the referenced Chapter-99 provisions with their additional rates, and a plain-language note. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"hts": {
"url": "https://gateway.pipeworx.io/hts/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/hts/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1865+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/hts_search \
-H 'Content-Type: application/json' \
-d '{"query":"lithium batteries"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/hts_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-hts is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/hts/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"hts": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-hts"]
}
}
}
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Hts data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT