Use this data from Claude

This data is available as a Model Context Protocol (MCP) server, so Claude can query it directly. It is read-only and uses the same data and limits as the JSON API.

Server URL

https://trackberry.com/data/mcp

Claude.ai

Open Settings, then Connectors, choose Add custom connector, and paste the server URL above. Name it "Market data".

Claude Code

Run:

claude mcp add --transport http market-data https://trackberry.com/data/mcp

With an API key (needed for top_exporters and exporter_profile):

claude mcp add --transport http market-data https://trackberry.com/data/mcp \
  --header "Authorization: Bearer <key>"

API key

Public tools work without a key. top_exporters and exporter_profile need an API key, sent as Authorization: Bearer <key> (or X-API-Key). An invalid key is rejected.

Tools

• list_products List tracked products: List the products with export data, the origins that track them, the available seasons, the current season and how fresh the data is. Start here to find valid origin and product values.
• weekly_volumes Weekly export volumes: Week-by-week export volume (net tonnes, USD FOB, average FOB USD/kg) of a product for one season, with boxes (commercial units declared in boxes), next to the same ISO (calendar) week a year before (`previous_tonnes`), and season to date on both sides (`cumulative_tonnes`, `previous_cumulative_tonnes`). Defaults to the current season. Recent weeks are provisional (`tonnes` is what is declared so far); when an estimate is reliable they carry `estimated_tonnes`, the estimate of the part not declared yet (the week's total estimate is tonnes + estimated_tonnes), with `estimate_basis` (fill_in: declared so far scaled up by the expected completeness `estimate_completeness`; manifests: from cargo manifests).
• destinations Export destinations: Breakdown of exports by destination country, port and region (market and sub-region, e.g. Europe / Northern Europe; net tonnes, USD FOB, share) for a period of shipment dates. Defaults to the current season.
• compare_seasons Compare seasons: Cumulative export volume (net tonnes) week by week for several seasons, to compare a running season with previous ones. Each week has its ISO calendar week (`iso_year`, `iso_week`): compare the same ISO week across seasons, as the trade does; `season_week` (week 1 = ISO week containing the season start) can differ by one between seasons. A running season stops at the latest data week.
• top_exporters (API key required) Top exporters: Ranking of exporters (tax id, name, net tonnes, USD FOB, market share, average FOB USD/kg) for a period of shipment dates. Defaults to the current season. Requires an API key.
• exporter_profile (API key required) Exporter profile: Profile of one exporter by tax id (RUC in Peru): totals, destinations, weekly seasonality and season-by-season volumes with change versus the previous season. Optionally restricted to one product. Requires an API key.
• vessel_departures Vessel departures: Recent vessel sailings carrying a product, per vessel and destination port: sailing date, vessel, destination port and country, shipping lines, confirmed tonnes and estimated tonnes (with bill counts). Confirmed = matched customs declarations (net weight). Estimated = shipments of known exporters whose declaration is not in yet (gross weight from the cargo manifest); recent sailings are mostly estimates because declarations arrive up to about 30 days after sailing. Each sailing has an expected arrival week (`estimated_arrival_iso_week`): sailing date + a typical direct transit time to the port, approximate (a transshipment adds 1-2 weeks), null for ports without one. Defaults to Europe and the last 30 days. Departure data comes from SUNAT export cargo manifests.

Volumes are net tonnes and values USD FOB. The data comes from SUNAT (Peru), definitive export declarations; recent weeks are provisional.

Rate limits

• Anonymous: 30 requests per 1 minute
• Authenticated: 300 requests per 1 minute