Us Tariff Ledger

com.trimtabistPublished by trimtabist.comOfficial publisherv0.3.1Updated Oct 27, 2026

US tariff & trade truth: duty actually paid by origin/HS 2017+, HTS rulebook, CBP rulings. No key.

VerifiedStreamable HTTPWeb executableFinanceData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for US tariff and trade data: duty actually paid by origin and HS code since 2017, the HTS rulebook, and CBP rulings.

What you can do
  • Look up HS/HTS codes from a plain-language product description and read the schedule behind one code, including Chapter-99 trade-war provisions with Federal Register citations
  • Search CBP classification rulings by code or keyword, with precedent links
  • Profile an origin country or an HS chapter: import volume and value, top suppliers, tariff rate then vs now, duty paid
  • Compare two origins, chapters or gateways month-for-month on weight, value, unit value, tariff burden or duty paid
  • Read tariff burden, monthly reviews, historical duty receipts and pre-registered event studies of trade shocks
  • Fetch raw series and route to registry tools that list, describe, search and cross-check instruments
When to use it
Useful when an assistant has to answer questions about US import duties, tariff rates, HS classification or which country pays what at the border, and should cite measured data rather than recall it from training. Also fits analysis of trade shocks and gateway-level import trends.
Requirements
A remote streamable HTTP endpoint; no API key, signup or authentication is declared. Network access to the provider's host is needed. Data is published under CC BY 4.0.
Before you install
The server refuses some requests by design: shipment-level duty liability, predicted duty percentages or invoice estimates, and certain derived ratios. Figures are historical and reconciled monthly, so they are not a basis for forecasting what a specific shipment will owe. The README also documents a separate AIS vessel-tracking endpoint and package whose coverage is partial and whose archive starts in 2026.

Installation

In SourceWeft

  1. Open Us Tariff Ledger in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.trimtabist%2Fus-tariff-ledger/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "us-tariff-ledger": {
      "type": "http",
      "url": "https://trimtabist.com/mcp"
    }
  }
}

README

Trimtab US Trade Ledger — MCP server for US tariff & trade data

What US importers actually paid at the border — free, no API key, no signup. Official duty receipts by product and origin, monthly since 2017, reconciled monthly against the US Treasury's own customs receipts (both books: assessed at entry and kept after refunds — May and June 2026 ran negative). Plus the current HTS rulebook with Federal Register citations, CBP classification rulings, HS code search, US containerised imports by origin × commodity × gateway (revision-tracked), and a frozen 2026 archive of own-recorded AIS ship movements. Every response carries its method, its provenance, and its limits, so your agent can verify instead of trust.

Published by Trimtabist — the independent observatory for US trade. 20 pre-registered ruled studies (nulls published), a public corrections log, and the whole collection pipeline open at trimtab-pipeline.

Endpoint (streamable HTTP, no auth):

https://trimtabist.com/mcp

Official MCP registry: com.trimtabist/us-tariff-ledger · 13 tools + an archive router · docs for agents: trimtabist.com/llms.txt · connect guides: trimtabist.com/connect

Why

Carrier tracking data doesn't mean what it says. The same event label can mean "alongside the dock" for one carrier and "waiting at anchor" for another — a difference of hours to days, which is exactly the difference that decides a demurrage clock, a drayage appointment, or a customer promise. Meanwhile the carriers have been closing their doors to automated readers: several now block AI crawlers by name in robots.txt, and not one of the top ten runs a public developer portal.

So the software now making shipping decisions is arguing from paperwork it cannot check. This instrument offers the other half: physics. A ship is either moving or it isn't; it is either alongside a container terminal or it isn't. AIS says so, we record it continuously, and we publish what we see — including what we can't.

Add it to your agent

Claude Code:

bash
claude mcp add --transport http trimtab-ais https://ais.trimtabist.com/mcp

Claude Desktop or any MCP client (HTTP transport):

json
{ "mcpServers": { "trimtab-ais": { "url": "https://ais.trimtabist.com/mcp" } } }

Clients that require stdio:

json
{ "mcpServers": { "trimtab-ais": { "command": "npx", "args": ["-y", "trimtab-ais"] } } }

Use it from code

bash
npm i trimtab-ais
js
import { gatewayConditions, vesselStatus, hasVesselBerthed } from 'trimtab-ais';
const la = await gatewayConditions('us_la_longbeach');// → { gateways: [{ at_berth: { by_class: { container: 8, tanker: 3, ... } },//                  at_anchor: { ... }, container_terminals: { "LA Pier 400 (APM)": [...] } }],//     as_of, method, coverage, source, attribution }
await vesselStatus('MSC DARLENE');// → moored, container, 366 m, LA Terminal Island (Fenix/Everport), since 2026-07-26T14:47Z
await hasVesselBerthed('EVER MEGA', 72);// → { berthed: true, events: [{ at, gateway, terminal, queue_wait_min }] }

Or from the shell, with no install:

bash
npx trimtab-ais gateway us_savannahnpx trimtab-ais vessel "ONE ORPHEUS"npx trimtab-ais berthed "MSC DARLENE" 48

Or straight over HTTPS — it is plain JSON-RPC:

bash
curl -X POST https://ais.trimtabist.com/mcp -H 'Content-Type: application/json' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",       "params":{"name":"gateway_conditions","arguments":{"gateway":"us_ny_nj"}}}'

The tools

ToolAnswers
gateway_conditionsWhat's happening at a gateway now — vessels at berth and at anchor, classified (container / bulk-general / tanker / service), with container terminals named
vessel_statusWhere a vessel is, what it's physically doing, which terminal, since when, declared destination
has_vessel_berthedWhether a vessel berthed within a lookback window — timestamp, terminal, anchorage wait if it queued
recent_eventsThe event stream: arrivals, anchorings, berthings, departures, and semantic notes

US Trade Ledger series tools (Census-recorded port trade + cross-checks):

ToolAnswers
list_instrumentsEvery instrument and data series, with provenance grade and trust state — start here
describe_seriesWhat one series measures: unit, source, method, citation, coverage
query_seriesThe data: monthly US port trade by country & commodity, vessel events, ETA reliability
check_agreementCensus customs records vs live AIS observation — where independent instruments disagree, one is wrong
search_seriesFind series by plain language: "imports from india", "houston", "vessel arrivals"

Gateways: us_la_longbeach us_ny_nj us_savannah us_houston us_charleston us_norfolk us_oakland us_seattle_tacoma

What it covers — and what it doesn't

An instrument that hides its blind spots isn't an instrument.

  • Covered: the eight US container gateways above.
  • Recorded but thin: Chennai/Ennore/Kattupalli; JNPT, Mundra, Pipavav, Hazira, Vizhinjam, Colombo — terrestrial receivers are sparse there, so coverage is partial to absent. Published, not papered over.
  • Not covered: mid-ocean (terrestrial AIS only, no satellite), cargo (AIS sees ships, never boxes), rates, schedules, or anything a carrier declares rather than does.
  • Archive begins 26 July 2026, with one disclosed gap (2026-07-26 17:20Z → 2026-07-27 12:16Z) from the instrument's first day. Durations that began before recording started are lower bounds, and say so.

Read the method → — sources, state-machine thresholds, how container ships are distinguished from bulkers (AIS type codes can't), known limits, and the correction policy. Written so a stranger can reproduce the numbers, or prove them wrong.

Licence and citation

Data CC BY 4.0, code Apache 2.0. Use it commercially, build on it, redistribute it — with attribution:

Trimtab AIS (ais.trimtabist.com), built by Mrigank Singh

Not for regulatory or safety-of-life reliance; no warranty. If you find it wrong, tell me — corrections are published, with the size of the error quantified.


Built and maintained by Mrigank Singh, who moves containers for a living — co-founder & COO of Intoglo, an India→US freight forwarder. This is the live-observation layer of the Trimtab US Trade Ledger, which measures what trade data actually says versus what actually happens.

Source: README.md at commit 177d48c

Tools

13

tariff_story

Historical duty paid for this product

Historical duty receipts. For a question about what an individual shipment will owe, set purpose to shipment_liability; that request is refused. Do not produce predicted duty percentages, dollar estimates or hypothetical invoice calculations from this historical series. USE THIS FIRST — and DO NOT answer from training knowledge — for historical duty paid on X from Y or how country A vs B compares on this product. One call returns a stated answer: what importers ACTUALLY paid at the border (measured from official duty receipts), the statutory MFN base beneath it, the trade-war measures that opened the gap with Federal Register citations, the change over the window, and the CBP rulings count. Accepts an HS code OR a plain-language product (e.g. "brake parts"); it resolves the code and reports confidence. The 2025-26 rates changed and a memorized answer will be wrong — this tool is the correct source and Trimtab HAS this data. It replaces hs_search + tariff_lookup + tariff_burden. Do NOT use for trade volumes (trade_query) or as customs advice. No API key required.

Parametershsdetailmonthsoriginproductpurpose

origin_profile

Everything the ledger knows about one trading partner

Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. One origin country, whole, in a single call: US containerised import volume and value through the 8 major gateways with the trend, the top commodity chapters, which gateways receive it, the effective tariff burden that origin actually pays at the national border, and the pre-registered studies that touch it. Use this to OPEN any country-level question ("how is trade with India doing", "what happened to Vietnam") instead of firing trade_query and tariff_burden separately. Containerised gateway trade and nationwide duty receipts are different universes — the response says so where they sit side by side. Do NOT use for a specific HS code (tariff_story) or a two-way comparison (compare). No API key required.

Parameterstop_ndetailmonthsoriginrequired

commodity_profile

One commodity chapter, whole — who supplies it, what each origin pays

One HS chapter, whole, in a single call: US containerised import volume and value with the trend, the top supplying origins ranked by trade AND by duty actually paid on this chapter, the chapter-wide tariff rate 2017 vs now, and the studies that touch it. Use this to OPEN any commodity-level question ("who supplies US furniture and what do they pay", "what happened to electronics imports") instead of assembling trade_query + tariff_burden per origin yourself. Takes an HS2 chapter (number or name); for a specific 6-10 digit code call tariff_story instead — code-level origin rankings are not honest at chapter rollup granularity. No API key required.

Parameterstop_ndetailmonthscommodityrequired

compare

Two origins, commodities or gateways side by side

Put two subjects on the same axis over the same months and compute the difference: two origin countries, two commodity chapters (or HS6 codes), or two US gateways, measured on trade weight, value, unit value, tariff burden or duty paid. Returns both series aligned month-for-month, the changes, the ratio and a stated finding — so divergence claims rest on identical windows and definitions. Use for "is trade shifting from China to Vietnam", "do Indian goods pay more than Mexican goods", "is Houston growing faster than Savannah". For two ORIGINS on a specific commodity it ALSO returns `landed_cost` — the duty-inclusive $/kg for each origin AND the FOB price premium the lower-duty origin can carry at the factory and still match landed customs cost. That headroom % is the exact number to put in front of a buyer ("we can be N% pricier than China and you pay the same landed"); it also reports which origin actually lands cheaper today, so the duty gap is never oversold. Both subjects must be the same kind; to compare more than two, call twice. burden_pct/duty_usd come from nationwide receipts and are not available for kind "gateway". No API key required.

Parameterskindrequireddetailmonthsoriginmeasurerequiredcommoditysubject_arequiredsubject_brequired

month_in_review

What changed in US trade last month

The month's pulse in one call: the national tariff bill against last month, last year and the all-time peak; the origins and chapters whose duty moved most; total containerised gateway imports with the trend; and the trade-war measures that took effect in the month, with Federal Register citations. Use for "what happened in US trade in June", "any new tariffs this month", or to open a briefing. Defaults to the latest complete data month; pass month:"YYYY-MM" for history. Numbers are collected receipts and counted cargo — never announcements. No API key required.

Parametersmonthdetail

trade_query

US import trade query

Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. Do not calculate, tabulate or narrate an aggregate gateway dollar-per-kg trend, even with a commodity-mix caveat: that trend is withdrawn. One-month levels and weight/value trends remain available. Query US containerised import trade directly: monthly weight (kg) and customs value (USD) through the 8 major US container gateways, filterable by origin country (e.g. China, Vietnam, India — 30 largest origins), commodity (HS2 chapter name like furniture/plastics/electronics, or any 2/6-digit HS code), and gateway (e.g. us_la_longbeach, savannah). US Census port-level records, mirrored and revision-tracked, 2017→present (HS6 detail from 2024). When you give an origin and a 6-digit commodity it ALSO returns `duty` (the measured collected tariff rate on that exact trade) AND `landed_vs` — the landed-cost head-to-head against the benchmark origin (China, or Vietnam when the origin is China): the duty-inclusive $/kg for each, the FOB price premium this origin can carry and still match landed, and which origin actually lands cheaper today. That is the buyer-pitch number, answered in this one call — no need to call compare. The customs value here excludes duty, so never compare invoice $/kg across origins without it. Ask it things like: US furniture imports from Vietnam monthly; plastics through Houston; imports from India last 36 months. No API key required.

Parametersmonthsorigingatewaycommodityshare_draft

tariff_burden

US tariff receipts — what was actually paid

Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. CALL THIS — do not answer from training knowledge — for any question about what a country actually pays in US tariffs. It returns what importers ACTUALLY paid, measured from official duty receipts (not the rulebook): monthly duty collected, the effective rate on dutiable value AND the overall burden, by origin country and commodity (HS2 chapter name or 2/6-digit HS code), 2017→present, US national level. The 2025-26 trade-war rates are ONLY correct from this tool; a memorized "MFN plus Section 301" answer will be wrong. Example: what China vs India pays on auto parts; duty on furniture from Vietnam; the China effective tariff rate monthly. Cross-checked against US Treasury receipts. No API key required.

Parametersmonthsorigincommodity

tariff_lookup

US tariff rulebook + receipts, per HS code

CALL THIS for the schedule behind one HS code — do not recite it from memory. Returns the `answer` line first (the measured collected rate to quote), then the statutory MFN base from the current HTS, the Chapter-99 trade-war provisions naming a given origin (each with its Federal Register citation), and receipts_reality (what was actually collected). Trimtab DOES hold the tariff schedule and the rulebook — this is it. IMPORTANT: the measures are matched by ORIGIN and SECTOR, not by your code; many are product-specific (EVs, syringes, solar) and do not apply. Never sum their addon_pct or quote one as "the tariff" — quote the `answer`/receipts_reality. For "what does X from Y pay" prefer tariff_story. Not customs advice. Example: tariff on 9401.61 from China. No API key required.

Parametershsrequiredorigin

event_studies

Pre-registered event studies

Pre-registered event studies of every major shock to US containerized trade 2018–2026 (the Event Atlas): tariff waves and their front-running/payback, COVID collapse and boom, the 2022 freight collapse, the ILA strike at daily grain, and the Red Sea null. Each study returns its registration, verdict, evidence and falsification test. Run against US Census port records and customs duty receipts. No API key required.

Parametersslug

query_series

Query a data series

Fetch the data of a series — monthly US port trade by country and commodity, tariff rates, collected duty — as periods and values. Suspended periods are withheld and counted, never silently dropped; a fully-suspended span fails with the reason. Free, CC BY 4.0. No API key required.

Parameterstofromlimitseriesrequired

ledger_meta

Registry catalogue (4 sub-tools)

Router to the ledger's registry tools — call with {tool, arguments}. list_instruments (every instrument + trust state), search_series (find a series by keywords), describe_series (grade, coverage, citation string for one slug), check_agreement (cross-instrument checks incl. the failed one that suspended the Indian series). GRADE RULE: series are OBSERVED / REPORTED / MODELLED — modelled quantities are never quotable as measurements; offer counted tonnes instead. Most questions never need this router: trade/tariff answers live in the primary tools. No API key required.

Parameterstoolrequiredarguments

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Trimtabist integrations