com.trimtabist/us-tariff-ledger
v0.3.1US tariff & trade truth: duty actually paid by origin/HS 2017+, HTS rulebook, CBP rulings. No key.
Endpoint health
online- Last checked
- 11/20/2026, 8:16:56 AM
- Latency
- 93 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.trimtabist%2Fus-tariff-ledger
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.trimtabist/us-tariff-ledger": {
"url": "https://trimtabist.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
13 shown · authentication unknown
One commodity chapter, whole — who supplies it, what each origin pays
commodity_profile
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.
Schema valid · SHA-256 89a31491b631…
View input schema
{ "type": "object", "properties": { "commodity": { "type": "string", "description": "HS2 chapter — number (\"94\") or name (\"furniture\"). Not a 6-digit code (use tariff_story for those)." }, "months": { "type": "integer", "minimum": 3, "maximum": 60, "default": 24 }, "top_n": { "type": "integer", "minimum": 3, "maximum": 20, "default": 8, "description": "How many origins to rank." }, "detail": { "type": "string", "enum": [ "answer", "standard", "full" ], "default": "standard" } }, "required": [ "commodity" ] }Two origins, commodities or gateways side by side
compare
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.
Connections
streamable-http
https://trimtabist.com/mcp