FreightCortex Archives - Zorost Intelligence | AI, Cloud & Data Experts https://zorost.com/tag/freightcortex/ Production AI systems for aviation, manufacturing, pharma, government, finance, freight, and geopolitical intelligence. Wed, 20 May 2026 18:52:41 +0000 en-US hourly 1 https://wordpress.org/?v=7.0 https://zorost.com/wp-content/uploads/2025/08/ZOROST-Intel-Logo3_512-150x150.png FreightCortex Archives - Zorost Intelligence | AI, Cloud & Data Experts https://zorost.com/tag/freightcortex/ 32 32 81719879 When Agents Call Agents: Why the MCP Server Matters in Freight https://zorost.com/mcp-server-freight-agents-call-agents/ Tue, 24 Feb 2026 09:00:00 +0000 https://zorost.com/mcp-server-freight-agents-call-agents/ Model Context Protocol lets external AI agents call FreightCortex tools natively. Here is why that matters — and what it unlocks for the freight intelligence stack.

The post When Agents Call Agents: Why the MCP Server Matters in Freight appeared first on Zorost Intelligence | AI, Cloud & Data Experts.

]]>

Pull-quote: “If your platform isn’t callable by other agents, your platform isn’t future-proof.”

Why this matters

The next generation of enterprise software is being shaped by a simple fact: users have agents now. Claude Desktop, custom internal agents, vendor-provided agents — they’re all going to call your platform. Either they call it through your REST API (and the agent has to know your URL structure, your authentication, your error semantics) or they call it through a standard protocol.

That standard is Model Context Protocol (MCP).

What MCP is

MCP is an open protocol developed by Anthropic and adopted across the agent ecosystem. It defines how an AI agent describes its tools, how a host (the agent’s runtime) discovers and calls those tools, and how results are returned. The result is a clean separation: tools are advertised, agents discover and call them, and you can swap tool servers without touching the agent.

For FreightCortex, the MCP server is a thin layer that exposes our 16 tools using the protocol. An external agent — a customer’s internal Claude Desktop, an OEM’s analytics chatbot, or a third-party tool — can connect to our MCP endpoint and use FreightCortex like a native tool.

What this unlocks

Three things:

  1. Native callability from any MCP-compatible agent. Customers do not need to write custom integrations. Their agent just connects to our MCP server.
  2. Composability with other tools. A customer agent can use FreightCortex tools alongside their own internal tools. The agent decides when to call which.
  3. Future-proofing. As the agent ecosystem grows, MCP-compatible platforms are accessible by default. REST-only platforms have to be manually integrated, one customer at a time.

What it requires

Three engineering investments:

  1. Tool contracts — every tool we want to expose has a typed schema. (We already had this.)
  2. The MCP server itself — a thin transport layer over those tools.
  3. Authentication and rate limiting — MCP doesn’t replace your existing auth; it sits on top of it.

A concrete example

An analyst is using Claude Desktop on her workstation. She asks “what’s driving the cost increase on the Atlanta–Dallas corridor?” Claude knows about the FreightCortex MCP server (configured once per workstation) and decides to use it. It calls query_corridor_metrics, compute_anomaly_score, query_carrier_metrics, and run_capacity_simulation — and produces an answer with the same structure as the answer it would have given inside the FreightCortex web app, except this time it is in her existing analyst environment.

The customer never had to log in to FreightCortex.

Closing

If your platform isn’t callable by other agents, your platform isn’t future-proof. MCP is how you make that callable. It is a small engineering investment with very high leverage.

The post When Agents Call Agents: Why the MCP Server Matters in Freight appeared first on Zorost Intelligence | AI, Cloud & Data Experts.

]]> 24291 An AI Freight Analyst with 16 Tools https://zorost.com/ai-freight-analyst-16-tools/ Tue, 11 Nov 2025 09:00:00 +0000 https://zorost.com/ai-freight-analyst-16-tools/ Most freight intelligence platforms add a chatbot. FreightCortex makes the analyst the center of the platform. Here is what an AI analyst with 16 callable tools actually does — and how it compares to a senior human analyst.

The post An AI Freight Analyst with 16 Tools appeared first on Zorost Intelligence | AI, Cloud & Data Experts.

]]>

Pull-quote: “The AI analyst is not a chatbot bolted on the side. It is the center of the platform.”

Why this matters

Most freight intelligence platforms have followed the same pattern with generative AI: keep the existing dashboards, add a chatbot in the corner, ship a press release. The chatbot answers FAQ-class questions and sometimes summarizes a dashboard. Senior freight analysts ignore it.

FreightCortex is built around the AI analyst, not the other way around. The analyst is a multi-tool agent with sixteen callable tools that can pull data, run statistical tests, run simulations, and produce structured outputs. It is more like a junior analyst with access to the full platform than like a chatbot.

The 16 tools

# Tool What it does
1 query_corridor_metrics Lane-level KPIs (cost, transit time, capacity, on-time %)
2 query_carrier_metrics Carrier-level KPIs and ranking
3 query_origin_destination_flows OD-pair flows with filters
4 compute_anomaly_score Z-score / isolation forest / CUSUM on a metric series
5 run_capacity_simulation What-if capacity reduction or expansion
6 run_demand_simulation What-if demand shock scenarios
7 run_disruption_simulation What-if disruption (port closure, weather, strike)
8 run_routing_simulation Reroute optimization under constraints
9 run_modal_shift_simulation Mode-shift impact (truck ↔ rail ↔ intermodal)
10 run_emissions_simulation CO₂ impact under scenarios
11 run_network_stress_test Network-wide stress scenarios
12 compute_shortest_path Multi-modal shortest path
13 compute_betweenness Node centrality
14 compute_communities Network communities
15 generate_report Compose structured report from analytical session
16 generate_chart Render a specific chart type with provided data

Each tool is a typed contract: inputs, outputs, and side effects are documented. Every call is logged with the requesting question, the parameters, the result, and timestamps.

Why typed tools matter

The single most important architectural decision in agent design is whether your tools have contracts. Untyped tools — give the model a vague description and let it improvise — are unreliable. Typed tools — with explicit input schemas, output schemas, and validation — are reliable.

FreightCortex’s analyst will not call a tool with an invalid input. The schema rejects the call before it reaches the data layer. That eliminates an entire class of failure that plagues unconstrained agents.

What this lets analysts do

A typical session: an analyst asks “what’s driving the cost increase on the Atlanta-Dallas corridor over the last quarter?” The analyst:

  1. Calls query_corridor_metrics for Atlanta-Dallas with a 90-day window
  2. Calls compute_anomaly_score on the cost series
  3. Calls query_carrier_metrics to see which carriers’ rates moved
  4. Calls run_capacity_simulation to test whether the increase tracks capacity changes
  5. Generates a structured report with charts

This is fifteen minutes of senior-analyst work. With FreightCortex, it is one question and a structured answer with citations.

Closing

A chatbot bolted on a dashboard is a feature. An AI analyst at the center of the platform is a product. The difference shows up the moment senior analysts compare them in real engagements.

The post An AI Freight Analyst with 16 Tools appeared first on Zorost Intelligence | AI, Cloud & Data Experts.

]]> 24290