tracking · eta
live MSCU 1234567 predicted
ETA 3 Jul 5 Jul
+2 days · Rotterdam congestion
predicted from observed delay, not a stale carrier promise
Ocean freight · built as components
Five instruments. One spine. Never dark.
Pick the sailing, price the lane, plan the box, watch it move: one shared data spine, cross-checked against 72,000+ sailings. Web, API, MCP.
Try a live sample:
A working sample of TrackingMCP. Your result opens on trackingmcp.com, no login needed.
A working sample of SchedulesMCP. Your lane opens on schedulesmcp.com, no login needed.
Prefer an account? Start free, no card →
Drop in one component, or the whole suite. One reference in; truthful status out.
MCP-native
Every product ships as Model Context Protocol tools.
Speaks DCSA
Carrier events normalised to the industry standard.
REST + Webhooks
HMAC-signed events and a clean JSON API.
CTU Code · IMDG
Load planning to the rules cargo ships under.
AIS-aware
Live vessel positions feed every ETA.
One data layer
Tracking, schedules and loading share a spine.
233 carriers
125 direct connectors · 186 SCACs recognised.
2–3 sources each
Independent fallback data paths per carrier.
4 AIS feeds
Live networks fused for positions, speed and ETA.
0–5 min freshness
Events land minutes after the carrier knows.
Why teams pick Navo24
The numbers behind the feed.
Every figure here is measured, not marketed: the same numbers the data spine runs on.
233
carriers covered
125 direct connectors, 2–3 fallback paths each, the long tail included.
0–5 min
event freshness
From the carrier knowing to your webhook firing.
72,000 +
sailings monitored
Forward sailings cross-checked against every tracked box.
110,000 +
AIS positions recorded
Vessel positions fused from 4 independent AIS networks.
24/7
A fix crew that never sleeps
An AI engineering agent watches every connector around the clock: it detects breakage, diagnoses it, and drafts the fix within minutes, with humans reviewing every change. That is why we are navo24.
DCSA
The standard the majors built
Every event normalised to the DCSA standard: the schema MSC, Maersk, CMA CGM, Hapag-Lloyd and ONE created and adopted themselves. Drops into your TMS without a translation layer.
MCP ×3
AI-native from day one
First-party MCP servers for tracking, schedules and loading: your agents buy and query without a sales call. No incumbent (Terminal49, Vizion, project44) ships one.
Also counted: 2,700+ vessels on file · 55,000+ port calls observed · 66,000+ schedule revisions caught · production database, July 2026.
The suite
Five tools. One spine.
Each is a complete product on its own domain, with its own free tier and its own API. They were built to be used apart, and to be worth more together.
trackingmcp.com TrackingMCP
Know where every container is, and when it will really arrive.
- 125 direct connectors · 233 carriers covered
- Events normalised to the DCSA standard
- HMAC-signed webhooks
aircargomcp.com AirCargoMCP
Track any air waybill, from acceptance to delivery, in one clean timeline.
- Major air-cargo carriers covered
- Cargo-IMP milestones normalised
- MCP tools + REST API
schedulesmcp.com SchedulesMCP
Compare sailings the way a freight desk actually books them.
- 5,000+ lanes · 255 ports
- 72,000+ forward sailings
- Reliability from observed arrivals
loadingmcp.com LoadingMCP
Plan the stuff inside the box: to the standard, not by eye.
- CTU Code · IMDG · EN 12195
- Axle & floor-strength limits
- Centre-of-gravity checks
freightratesmcp.com FreightRatesMCP
See what a lane costs this week, before you brief a forwarder.
- Live spot rates, refreshed daily
- Rate trend + on-time on every lane
- Hundreds of ex-Asia lanes
Why a suite, not five tools
One shipment, four steps, on a single spine.
Pick the sailing on Schedules, price the lane on FreightRates, plan the box on Loading, then watch it move on Tracking. It is how a shipment gets booked, and every step runs on one shared data spine, so each makes the next smarter.
- Take only what you need
- Each product stands on its own: a tracking webhook, a schedule lookup, a load plan. Adopt one tool today; the rest are there when you want them. No platform migration, no rip-and-replace.
- They share one spine
- The steps feed each other: Schedules scores reliability from the arrivals Tracking actually observed; Loading and FreightRates read the same lane truth. One shared data spine, so each part makes the next smarter, worth more together than apart.
- Built for your software, and your AI
- Native MCP tools an assistant can call, a REST API your stack can hit, and webhooks that push. Plug a single component into what you already run; no front-end of ours required.
Take one step today; the rest are here when you need them.
Live console
Not screenshots: the suite, doing the thing.
Every surface the suite exposes, live and droppable. Here they are, running, not described.
Free time 0 of 5 days left
free until 10 Jul · act before it starts
Point Claude, ChatGPT or your own agent at navo24; it calls the tools directly.
Utilisation0%
40HC · 15 pallets · 1 slot free · hover to repack
schedules · reliability
MSC TERESAbest
MSC · ZIM82%
ONE TRUST
ONE74%
EVER ACE
EMC61%
tracking · port congestion
berth waits Long Beach 5.1d
Rotterdam 3.2d
Antwerp 2.4d
Singapore 1.0d
tracking · ais radar
live In range 0 vessels
MSC TERESA 12.4 kn → Rotterdam
From the desk
Notes on moving boxes well.
2 Jul 2026
Container tracking API vs MCP: how AI agents track ocean freight
A REST tracking API makes your code do the work. An MCP server lets an AI agent do it in one tool-call. Here is the real difference for anyone wiring ocean-freight visibility into an assistant.
2 Jul 2026
The container packing checklist a weighbridge can't argue with
A loader's field checklist for packing to the CTU Code: VGM, weight distribution, centre of gravity, segregation and securing, with the two diagrams that stop a legally-stuffed box becoming an illegal truck.
2 Jul 2026
MSC demurrage & detention free time, port by port: how to read it
Demurrage and detention are two different clocks, and most shippers misread which one is running. Here is how MSC free time actually works, why it changes by port, and how to check the live figure before the charges start.
Questions
The things people ask first.
Straight answers on what Navo24 is, what MCP-native buys you, and how to start with a single component.
What is Navo24?
Navo24 is a hub for five composable, MCP-native freight products: TrackingMCP for container tracking, AirCargoMCP for air waybill tracking, SchedulesMCP for sailing schedules and lane reliability, FreightRatesMCP for ocean spot rates, and LoadingMCP for load planning. Each is a complete product with its own free tier and API; they share one data spine, so you can take one tool today and add the rest later.
What does “MCP-native” mean?
Every capability ships as a Model Context Protocol tool an AI assistant can call directly in plain language, not just a REST API you have to wrap in your own integration code. The same functions are also available over REST and webhooks, behind one key.
Do I have to adopt the whole suite?
No. Each product stands on its own: a tracking webhook, a schedule lookup, a load plan. Adopt one tool today; the rest are there when you want them. There is no platform migration and no rip-and-replace.
How is Navo24 different from a hosted visibility dashboard?
A dashboard is something your team logs into. Navo24 is components your software and your AI agent call: MCP tools, a REST API and webhooks you wire into the systems you already run, with no front-end of ours required.
Which carriers and lanes do you cover?
TrackingMCP covers 233 carriers: 125 direct connectors, 186 SCACs recognised, with events normalised to the DCSA standard. SchedulesMCP covers 5,000+ lanes and 255 ports with 72,000+ forward sailings, refreshed weekly, with reliability scored from arrivals we actually observed.
Can I try it without a sales call?
Yes. TrackingMCP has a real free tier of 5 active containers and 100 MCP calls a month, no card, and there is a no-login public container tracker. Every product self-serves; pick the tool that hurts most right now and start there.
Before you commit
The four doubts, answered straight.
What happens when a carrier redesigns their site at 2am?
Nothing you notice. Every carrier has 2–3 independent data paths: an official API, our own connector via a 3-provider proxy failover, and a cross-checked network source. Connectors self-heal by re-minting credentials and re-probing live boxes. Failover is automatic; your feed keeps flowing.
Is the free tier actually free, or a demo that expires?
It is real and it does not expire: 5 active containers and 100 MCP calls a month on TrackingMCP, no card required. Enough to wire it into a live workflow before you spend a euro.
We are not doing anything with AI agents yet. Is this still for us?
Yes. Everything ships as a plain REST API with HMAC-signed webhooks behind the same key; you can ignore MCP entirely. When your team does adopt agents, the tools are already there; nothing to migrate.
How does this compare to Vizion or project44?
Printed prices and a self-serve free tier instead of a sales cycle; 233 carriers with 2–3 fallback sources each; schedule-enriched ETAs on 5,000+ lanes; and first-party MCP servers no incumbent ships. The detailed, honest breakdowns are on our compare pages.
Weighing us against an incumbent? Read the honest comparisons →
Start with one component
Track a box, book a sailing, or pack a container, today.
TrackingMCP's free tier is real: 5 active containers, 100 MCP calls a month, no card. Prove the value on your own boxes first.