Data Collection
trimtabist.com
Provides real-time vessel tracking and status information for container gateways.
ENDPOINT 1
https://ais.trimtabist.com/mcp
MCP server metadata
- Name
- trimtab-ais
- Version
- 0.1.0
Own-recorded AIS truth for US container gateways (+ India, partial). Own-recorded terrestrial AIS. Zones: 8 US container gateways (LA/Long Beach, NY-NJ, Savannah, Houston, Charleston, Norfolk, Oakland, Seattle-Tacoma) + Chennai (partial) + JNPT/Mundra/Pipavav/Hazira/Vizhinjam/Colombo (recorded; currently little/no terrestrial coverage). Mid-ocean not covered. Archive begins 2026-07-26 (gap 2026-07-26T17:20Z→2026-07-27T12:16Z, disclosed). Built by Mrigank Singh — mriganksingh.ai
Known tools 9
gateway_conditionsCurrent conditions at monitored container gateways: vessels at berth and at anchor, broken down by vessel class (container / bulk-general / tanker / other), with container-terminal breakdown.
Potential side effectsvessel_statusLast observed status of a vessel by name (partial ok) or MMSI: position, physical state (underway/anchored/moored), zone, terminal if berthed at a known container terminal, speed, declared destination.
Potential side effectshas_vessel_berthedWhether a vessel has berthed (moored) at any monitored gateway within a lookback window.
Inferred read-onlyrecent_eventsRecent detected events (ZONE_ENTER/LEAVE, ANCHOR_START/END, BERTH_START/END, DEPARTED, SEMANTIC_NOTE) at monitored gateways.
Inferred read-onlylist_instrumentsThe catalogue: every Trimtab instrument and the series it publishes, with provenance grade (observed / reported / modelled), time horizon, coverage, and whether each series is currently fit to publish.
Potential side effectsdescribe_seriesFull detail for one series: what it measures, its unit, its source and method, how it should be cited, what it covers, and its current trust state.
Inferred read-onlysearch_seriesFind series by plain-language terms across names, descriptions, instruments and units.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.trimtab-ais]
url = "https://ais.trimtabist.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"trimtab-ais": {
"type": "http",
"url": "https://ais.trimtabist.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: trimtab-ais
Remote MCP URL: https://ais.trimtabist.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"trimtab-ais": {
"url": "https://ais.trimtabist.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"trimtab-ais": {
"type": "http",
"url": "https://ais.trimtabist.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "trimtab-ais",
"transport": "streamable-http",
"url": "https://ais.trimtabist.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://trimtabist.com/mcp
MCP server metadata
- Name
- trimtab-ais
- Version
- 0.3.0
The Trimtab US Trade Ledger: verified ground truth on the physical economy of US trade. Free, no key. START HERE — three tools answer most questions in one call: - tariff_story(hs or product, origin) — what it costs to import something, and what changed. Replaces hs_search + tariff_lookup + tariff_burden. - origin_profile(origin) — a trading partner whole: volumes, top commodities, gateways, tariff burden, trend. - compare(kind, subject_a, subject_b, measure) — two origins, commodities or gateways on one axis with the arithmetic done. - commodity_profile(commodity) — one HS chapter whole: who supplies it, what each origin pays on it. - month_in_review(month?) — the month's pulse: the bill, the biggest movers, the measures that took effect. Then the raw instruments: trade_query (containerised import volume/value by origin x commodity x gateway), tariff_burden (nationwide paid-rate history from duty receipts), tariff_lookup (raw schedule lines and Chapter-99 measures with Federal Register citations), rulings_search (CBP classification case law), hs_search (product -> candidate codes), event_studies (pre-registered findings, nulls included), and five registry tools (list_instruments / search_series / describe_series / query_series / check_agreement) for the graded, citable series catalogue. TWO RULES THAT PREVENT WRONG ANSWERS: 1. Never quote a Chapter-99 addon_pct as "the tariff." Those measures are matched by origin and sector, not by your code; many are product-specific. The measured collected rate from receipts is the composed truth — quote that. 2. trade_query counts containerised seaborne goods at 8 gateways. tariff_burden counts everything cleared nationwide by sea, air and land. Different universes; never divide one into the other. The registry catalogue and the frozen AIS archive (2026-07-26 to 2026-08-06 only; live recording retired 2026-08-08 — nothing current) are reached through one router: ledger_meta({tool, arguments}) with sub-tools list_instruments / search_series / describe_series / check_agreement / gateway_conditions / vessel_status / has_vessel_berthed / recent_events. Grades bind everywhere: OBSERVED / REPORTED / MODELLED — a modelled quantity (TEU is gross tonnage ÷ 11) is never quotable as a measurement. Errors here are instructions: they carry did_you_mean and a retry_with object you can pass straight back. Every response carries citations and caveats — quote them.
Known tools 13
tariff_storyThe complete tariff answer for one product from one origin, in a single call: what importers ACTUALLY paid at the border (measured from official duty receipts), the statutory MFN base rate beneath it, the trade-war measures that opened the gap with their Federal Register citations, the shape of the change over the window, and the CBP rulings count on the code.
Potential side effectsorigin_profileOne 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.
Inferred read-onlycommodity_profileOne 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.
Potential side effectscomparePut 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.
Potential side effectsmonth_in_reviewThe 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.
Potential side effectstrade_queryQuery US containerised import trade directly: monthly weight (kg) and customs value (USD) through the 8 major US container gateways, filterable by origin country (e.
Potential side effectstariff_burdenWhat US importers ACTUALLY paid in tariffs, measured from official receipts — not the rulebook: monthly duty collected, dutiable value and consumption value by origin country and commodity (HS2 chapter name or 2/6-digit HS code), 2017→present, US national level.
Inferred read-onlytariff_lookupRaw tariff-schedule lookup for one HS code: the statutory MFN base rate from the current Harmonized Tariff Schedule, the Chapter-99 trade-war provisions that name a given origin (each with its Federal Register citation), and what was actually collected at the border on that code from official duty receipts.
Potential side effectshs_searchFind the HS/HTS code for a product by describing it in plain words — the entry point to every tariff question.
Inferred read-onlyrulings_searchSearch US Customs (CBP) classification rulings — the case law of HS codes: how the border actually interprets what product belongs under which code.
Inferred read-onlyevent_studiesPre-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 LA/LB queue crisis and the hidden-queue mechanism, the 2022 freight collapse, the ILA strike at daily grain, the Red Sea null, and the AIS-vs-Census cross-check.
Potential side effectsquery_seriesFetch the data of a series — monthly US port trade by country and commodity, vessel events, ETA reliability — as periods and values.
Potential side effectsledger_metaRouter to the ledger's meta and archive tools — call with {tool, arguments}.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.trimtab-ais]
url = "https://trimtabist.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"trimtab-ais": {
"type": "http",
"url": "https://trimtabist.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: trimtab-ais
Remote MCP URL: https://trimtabist.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"trimtab-ais": {
"url": "https://trimtabist.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"trimtab-ais": {
"type": "http",
"url": "https://trimtabist.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "trimtab-ais",
"transport": "streamable-http",
"url": "https://trimtabist.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for trimtabist.com was fetched 2026-07-31T04:19:06.984Z.
trimtabist.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.