INDIVIDUAL MCP TOOL

shipment_status

Everything Aeroz holds about one shipment: profile and thresholds, status, items, custody events with their chip verification, the telemetry assessment (min/max/mean temperature, mean kinetic temperature, minutes out of range, peak shock, whether an excursion is open), the ranked routes, and open findings.

aeroz.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://api.aeroz.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for shipment_status and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

aeroz.io

CONNECT 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.aeroz]
url = "https://api.aeroz.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "aeroz": {
      "type": "http",
      "url": "https://api.aeroz.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: aeroz
Remote MCP URL: https://api.aeroz.io/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": {
    "aeroz": {
      "url": "https://api.aeroz.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "aeroz": {
      "type": "http",
      "url": "https://api.aeroz.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "aeroz",
  "transport": "streamable-http",
  "url": "https://api.aeroz.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

verify_chip — Verify that a physical item is genuine by checking its Aeroz chip UID and cryptographic signature.
check_recall — Check whether a specific unit is subject to an active recall.
dpp_readiness — Assess how ready a product category is for an EU Digital Product Passport, against the delegated act that applies to it.
list_findings — List findings raised by the Aeroz compliance agents watching this organisation — recall hits, DPP data gaps, regulatory changes, dwell anomalies, and clone detections.
list_agents — List the Aeroz compliance agents available to this organisation and which are currently enabled.
get_usage — Return this organisation's Aeroz verification volume and outcome breakdown over a recent period.
list_sandbox_chips — List the seeded sandbox chips for this organisation, including the UID and signature needed to call verify_chip.
onboarding_status — Report where this organisation stands in Aeroz onboarding: current stage, percentage complete, health, the single next action, and every open step with which side owns it.