Aeroz

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody.

Add to your agent

Copy this into your MCP client config:

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

Measured tools (28)

• verify_chip

  Verify that a physical item is genuine by checking its Aeroz chip UID and cryptographic signature. Use this before trusting any claim about a physical unit — a database record proves a record exists, not that the object in front of you is the one it describes. Returns verified:false with a reason and NO product data when the signature does not match.

  Parameters:

  • uid (required) — string — The chip UID read from the NFC tag or QR payload.
  • signature — string — The HMAC signature from the tag payload (the `t` parameter).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• check_recall

  Check whether a specific unit is subject to an active recall. Returns the recall reason, severity and date when one applies. Use this whenever a unit is about to be shipped, sold, dispensed, or installed.

  Parameters:

  • uid (required) — string — The chip UID of the unit to check.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• dpp_readiness

  Assess how ready a product category is for an EU Digital Product Passport, against the delegated act that applies to it. Returns the required data fields, which are present, and which are missing. IMPORTANT: this is a readiness signal, not a legal compliance determination — never report its output as confirmation that a product is compliant.

  Parameters:

  • category (required) — string — Product group, e.g. "batteries", "textiles", "iron_steel", "furniture", "tyres", "aluminium".

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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. Use this to answer "what needs my attention".

  Parameters:

  • limit — number — Maximum findings to return (default 25, max 200).
  • severity — string — Filter by severity.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_agents

  List the Aeroz compliance agents available to this organisation and which are currently enabled. Use this to explain monitoring coverage or to find an agent worth enabling.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_usage

  Return this organisation's Aeroz verification volume and outcome breakdown over a recent period. Use for reporting on scan volume, authentication failure rates, and trend.

  Parameters:

  • days — number — Days to look back (default 30, max 365).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_sandbox_chips

  List the seeded sandbox chips for this organisation, including the UID and signature needed to call verify_chip. Sandbox only — use when building or testing an integration before physical chips ship.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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. Use this to answer "what do we still need to do", "why are we not live yet", or "what is Aeroz waiting on". Steps marked side="aeroz" are Aeroz's obligation, not the customer's — say so plainly rather than presenting them as homework.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• onboarding_next_step

  Return only the single most important next action and how to complete it. Use when the user asks what to do next and does not want the whole checklist.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• complete_onboarding_step

  Mark a manual onboarding step complete on behalf of this organisation. Only steps the customer owns and that Aeroz cannot verify automatically can be set this way; an automatically verified step will refuse, because a self-report that contradicts the platform data is worse than no report. Pass the step key from onboarding_status.

  Parameters:

  • key (required) — string — The step key, e.g. "gs1_prefix" or "carrier_chosen".
  • note — string — What was done, for the audit trail.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• business_brief

  The full picture of this business as Aeroz holds it: declared product categories with their mandate dates and whether each date is fixed or provisional, onboarding state, open findings, and — importantly — which recall sources are NOT being monitored. Use this to orient before answering anything about the account. Never present an empty findings list as evidence of safety without also reporting coverage_gaps.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• ask_agent

  Ask this organisation's dedicated Aeroz agent a question in plain language and get a grounded answer. Use it for anything a human at the business would ask their account manager: "what do we still need to do", "when is our deadline", "what is Aeroz waiting on", "what is not being monitored", "how do we go live". The answer carries `grounded`: `computed` means it was read directly from the account's own data; `model` means a model composed it from that data and every date and figure was checked against it; `declined` means the agent does not hold what the question needs and said so — relay that honestly rather than filling the gap yourself. Asking never sends anything or changes the account.

  Parameters:

  • question (required) — string — The question, as the person asked it.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• agent_conversation

  The recent conversation between this organisation and its Aeroz agent, across the dashboard, MCP and email. Use it to see what has already been asked and answered before asking again.

  Parameters:

  • limit — number — Turns to return (default 20, max 60).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_shipment

  Register a shipment of physical items under a sensitivity profile so Aeroz can watch it in transit. Profiles: cold_chain (2–8 °C, mean kinetic temperature), frozen (≤ −15 °C), ambient_crt (15–30 °C, MKT ≤ 25), fragile (shock, tilt), high_value (light = container opened, dwell, chip-verified custody at every handoff), standard (movement only). Origin and destination need decimal-degree coordinates. Items may carry a chip uid, GTIN, lot and serial. Returns the shipment id and the thresholds that will judge it.

  Parameters:

  • origin (required) — object
  • destination (required) — object
  • items — array
  • carrier — string
  • profile — string
  • reference — string — Your own reference (PO, ASN, waybill).
  • thresholds — object — Optional overrides of the profile defaults (temp_min_c, temp_max_c, mkt_max_c, shock_crit_g, dwell_max_min, …).
  • planned_arrive — string — ISO 8601
  • planned_depart — string — ISO 8601

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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. Use for "where is it", "is the cold chain intact", "was it ever opened". An open excursion on a cold-chain lane means the load must be quarantined on arrival pending QA — say so.

  Parameters:

  • shipment_id (required) — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_shipments

  List this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).

  Parameters:

  • limit — number
  • status — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• log_telemetry

  Record sensor readings for a shipment — position, temperature, humidity, shock, tilt, light, battery — up to 500 per call. Aeroz judges the whole recent stream against the lane's thresholds immediately and returns the assessment and any findings raised. A shipment in `planned` moves to `in_transit` on its first reading.

  Parameters:

  • shipment_id (required) — string
  • readings (required) — array

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• record_custody

  Record a custody event on a shipment: pickup, checkpoint, handoff, delivered, exception or note. Pass the chip `uid` (and `signature`) read at the handoff and Aeroz verifies it on the spot, turning a signature on a form into proof of presence. On a high_value lane a handoff without a verified chip raises a finding. `pickup` moves the shipment to in_transit; `delivered` closes it.

  Parameters:

  • shipment_id (required) — string
  • kind (required) — string
  • lat — number
  • lng — number
  • uid — string
  • note — string
  • actor — string
  • location — string
  • signature — string
  • occurred_at — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• plan_route

  Compute and rank routes for a shipment at a departure time, scored for its sensitivity profile: traffic-aware duration and delay, ambient heat or cold along the way against the lane's ceiling, and rain, snow or gusts. Lower score is better and only comparable within one computation. The best route is marked chosen. The response says plainly when routing or weather data was unavailable and the ranking is time-only — relay that; a straight-line estimate is not a traffic-aware route.

  Parameters:

  • shipment_id (required) — string
  • depart_at — string — ISO 8601; defaults to the planned departure or now

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• shipment_profiles

  The sensitivity profiles Aeroz can judge a shipment against and the exact thresholds each applies, plus whether traffic and weather providers are configured for this deployment.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• bind_graded_item

  Bind an Aeroz chip to a graded collectible slab (PSA, CGC, SGC, BGS, TAG). The chip UID, grader, cert number, grade and card identity are signed together, so the chip vouches for exactly this label: a label moved to another holder, or a cert reprinted on a copy, shows as "binding broken" on a buyer's tap. For PSA, the cert is cross-checked against PSA's own record when PSA_API_TOKEN is configured; a disagreement flags the item. Returns the public verify URL to encode in the slab's QR. This does NOT grade the card and does not claim the card was unaltered before sealing — never present it as either.

  Parameters:

  • uid (required) — string — Chip UID bonded to the slab.
  • grader (required) — string
  • cert_number (required) — string
  • grade (required) — string — As printed: "10", "9.5", "8 OC", "Authentic", "Authentic Altered".
  • title (required) — string — e.g. "2003 Topps Chrome LeBron James #111"
  • year — string
  • public — boolean — Resolvable by a public tap (default true).
  • subject — string
  • variety — string
  • category — string
  • set_name — string
  • sealed_at — string
  • sealed_by — string
  • card_number — string
  • back_image_url — string
  • front_image_url — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• graded_item

  A graded item as Aeroz holds it: grader, cert, grade, identity, whether the grader's own record matched, how many times it has been verified by tap, and its full provenance chain (sealed, sold, consigned, vaulted, shipped, verified…). Use for "is this slab the one that was sealed", "where has it been", "has anyone tried to pass off a copy". Report what this proves AND what it does not.

  Parameters:

  • item_id (required) — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• record_provenance

  Append an event to a graded item's chain: sold, consigned, vaulted, withdrawn, shipped, received, flagged, note. Events are append-only and, when public, appear on the buyer's tap page. `flagged` marks the item and needs a note saying why.

  Parameters:

  • item_id (required) — string
  • kind (required) — string
  • note — string
  • actor — string
  • public — boolean
  • location — string
  • occurred_at — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_graded_items

  List this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).

  Parameters:

  • limit — number
  • status — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• my_section

  Return everything the Aeroz agent has built for this organisation: the regulatory calendar with only ADOPTED dates, the passport scaffold per product showing exactly which fields are missing, the identifier audit, the GS1 route, monitoring coverage, integration readiness, and the pre-filled audit scope. Each block carries a confidence — `computed` is derived from this account's own data and needs no review; `sourced` and `drafted` came from outside the platform or involved judgement and are cited. Use this to answer almost any question about what this business needs to do. Report a block's confidence when you rely on it, and never present a `drafted` block as settled.

  Parameters:

  • block — string — Optional. One of: calendar, passport, identifiers, gs1, coverage, integration, audit_scope, packet, profile, regimes, contacts, carrier.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• trace_unit

  The whole history of one serialized unit: every custody hop from commissioning to dispensing, whether the append-only log has been tampered with, and what each regulation makes of it. Use this to answer "where has this been", "who handled it", "is its record trustworthy" and "does this unit pass DSCSA / the EU passport rules". Every failing check cites the clause it enforces — quote the clause, not just the verdict. IMPORTANT: verdicts are readiness signals, never a legal compliance determination, and the response says so. Never report one as confirmation that a product is compliant.

  Parameters:

  • unit_id (required) — string — The unit id (cun_...). Use find_unit first if you only have a scan.
  • pack — string — Optional: "dscsa" or "dpp". Omit to judge under every pack.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• find_unit

  Resolve anything a scanner or a person can produce — a chip UID, a GS1 Digital Link URI, or a GTIN plus serial — to a unit, and return its history and verdicts. This is the tool for "what is this thing in front of me". An identifier that resolves to nothing is NOT the same as one that fails verification: the first means we have never seen it, the second means we have and it did not check out. Report them differently.

  Parameters:

  • uid — string — Chip UID read from a tap.
  • upi — string — Unique product identifier — usually a GS1 Digital Link URL.
  • gtin — string
  • serial — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• chain_readiness

  Sweep this organisation's units and report which regulatory checks are failing across the portfolio, how many units each affects, and examples to open. This is the tool for "which of my units have a broken custody chain", "what is failing right now", "what will not pass on 18 February" and "how are we doing overall". Counts are exact for the units swept; the response says when it hit its cap rather than implying it saw everything. An empty findings list means nothing failed among the units swept — it does not mean the organisation is compliant.

  Parameters:

  • pack — string — Optional: "dscsa" or "dpp". Omit to sweep under every pack.
  • limit — number — Units to sweep, default 100, maximum 300.
  • status — string — Optional: only units in this state (in_transit, in_stock, dispensed, recalled...).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.