CargoAi

No. None of the six tools books, quotes commercially or cancels anything. CargoAi's platform does book — its CargoCONNECT API documents a booking endpoint, a cancellation endpoint and a FlyWINDOW one-click flow — but none of those are wired into the MCP server. The connector searches rates and reads status. Committing to capacity still happens in CargoMART or through the REST API, by a person.

No. A rate search returns airline pricing and schedules, not an offer you have accepted. CargoAi documents that bookability varies by rate type and routing: market rates cannot be booked through the API at all, and import or cross-trade searches return options explicitly marked non-bookable via API. Treat a returned rate as an indication to act on, not a price you are committed to.

Yes, and this is the connector's one outbound path. Subscribe to Shipment Tracking takes an emails array, and every address in it starts receiving CargoAi tracking notifications for that AWB. The agent supplies those addresses as a tool argument, so a mistyped or hallucinated address subscribes a stranger. The matching unsubscribe tool reverses it, which makes the action recoverable rather than harmless.

Only identity claims. CargoAi's RFC 9728 descriptor and its authorization-server metadata both advertise exactly three scopes on 2026-08-22 — openid, email and profile. None of them names a CargoAi resource, so there is no scope that grants reading a shipment without also granting the email-subscription tools. The consent screen cannot separate the four reads from the two writes.

A CargoMART Premium or Ultimate office plan. CargoAi's connector documentation states this plainly and adds that Free and Basic plans have no access, with the error message MCP access requires a CargoMART Premium plan naming the failure. Upgrading is not self-service — CargoAi directs you to your account manager or to support@cargoai.co to change the office plan.

Six, and unusually both sources agree. Anthropic's directory snapshot lists six tool names and CargoAi's own connector documentation describes six tools with matching parameter tables. Neither list is longer than the other in either direction. That agreement is rare enough to be worth stating, though it rests on two published lists rather than on a handshake we could run ourselves.

It forwards queries and keeps nothing. CargoAi's connector documentation states the MCP server stores no conversation data and that each request is stateless. Search parameters, AWB numbers and any email addresses you pass are transmitted to CargoAi's internal APIs to fulfil the call. Operational logs are kept for 30 days and CargoAi states they are not shared outside its own infrastructure.

Anthropic's directory publishes a Claude Code command for it, but CargoAi does not document that path. CargoAi's setup instructions cover Claude.ai on the web and Claude Desktop only, and list a Claude account as the prerequisite. The endpoint uses standard OAuth with a registration endpoint advertised, so a client that performs dynamic registration should work — untested by us.