Uk Trade Tariff MCP server

@pipeworx/uk-trade-tariff

The UK Integrated Online Tariff from HMRC's trade-tariff service — commodity codes, third-country and preferential duty rates by origin, VAT and excise, import/export conditions, and live tariff-rate quota balances.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

from a plain-English product description, or resolve a numeric code.

• uktariffsearch(query, limit?, declarableonly?) — find a commodity code

10-digit code, with measures resolved against the JSON:API included graph.

• uktariffcommodity(code, origin?, maxmeasures?) — full duty detail for one

— tariff-rate quotas with remaining balance and status.

• uktariff_heading(heading, limit?) — the codes under one 4-digit heading.
• uktariffquota(ordernumber?, goodsnomenclatureitemid?, geographicalarea_id?, year?, critical?, limit?)

Auth

Keyless.

Data sources

• — classification search.
• — duties and measures.
• — heading contents.
• — TRQ balances.

Things worth knowing:

every /api/v2 path to the documentation site with content-length: 0, so a client that follows redirects gets a 200 and an empty body — a call that looks successful and returns nothing.

• The host is www., not api.. api.trade-tariff.service.gov.uk 301s

because "beans" is not in the nomenclature, while q=roasted coffee returns 40 commodities. Both are 200s with three empty arrays, which reads as "the UK does not tariff coffee". uktariffsearch therefore drops trailing words until something matches and reports queryused and narrowedtomatch.

• Fuzzy search ANDs every term. q=roasted coffee beans matches nothing

{type: "exact_match", entry: {endpoint, id}} with no result arrays at all.

• /search is polymorphic. A numeric query returns

intermediate subheading line) and once with "80" (the declarable leaf). They carry different descriptions, so without the suffix it looks like contradictory duplicates.

• A heading lists each code twice, once with producline_suffix "10" (the

status. Filter on year / order_number / area / commodity and read it off.

• /quotas/search rejects status= with a 400 even though every row has a

• Only declarable: true codes may be used on a customs declaration.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "uk-trade-tariff": {
      "url": "https://gateway.pipeworx.io/uk-trade-tariff/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/uk-trade-tariff/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, 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:

Shortened. The full README is on GitHub.