# Aeroz [Health: Active]

**Category:** 🏭 Industrial & IoT  
**Repository:** https://aeroz.io/  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aeroz

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

## Tools
Capabilities this server exposes over MCP:

- **verify_chip** — Verify a physical item by its Aeroz chip: the UID plus whatever signature the tap carried. Same answer as GET /v1/verify. 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. Read `proof` and `proves`: proof "presence" means the chip answered a fresh one-time SUN challenge (picc_data + cmac) and was physically there at this tap; proof "identity" means the static `t` signature is the one Aeroz issued for this UID, which a copied tag also carries. verified:false with reason "no_signature" (recognised:true) proves NOTHING about the item — only that the number is on the register. "signature_unchecked" means the signature was not compared (not a mismatch). A failed signature returns NO product data. Each call records the tap and spends the chip's one-time answer, so pass each SUN tap once. A sandbox key answers its seeded sandbox chips as fixtures (mode "sandbox" with a _warning) and any other UID from the register (mode "sandbox", register:true), so a sandbox company can check the test tags it minted.
- **check_recall** — Check whether a specific unit is subject to an active recall, from the register: reads only, verifies no signature and spends no chip answer. Returns known (on the register), recalled, and the recall reason, severity, date and id when one applies. recalled:null means the status is UNKNOWN (the UID is not on the register, or the register could not be read) — never report that as "not recalled". This says nothing about whether the item is genuine; use verify_chip for that. Use whenever a unit is about to be shipped, sold, dispensed, or installed. A sandbox key answers its seeded sandbox chips first and any other UID from the register (register:true).
- **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.
- **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".
- **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.
- **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. The buckets — authentic, recalled (any tap whose answer carried a recall, verified or not), mismatched (failed static or SUN signature), not_found, unverified (no or unchecked signature, test tag, held or disabled unit) and other — always sum to total.
- **list_sandbox_chips** — List the seeded sandbox chips for this organisation, with the UID and signature to pass to verify_chip, one per scenario: authentic, recalled, signature_mismatch (listed with a deliberately WRONG signature) and not_found (a UID that is not on the register). Sandbox only — use when building or testing an integration before physical chips ship.
- **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.
- **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.
- **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.
- **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.
- **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 refreshes the account's onboarding state and records the question and answer in the conversation (see agent_conversation). It sends nothing outside Aeroz and changes no product, shipment or passport data.
- **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.
- **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.
- **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.
- **list_shipments** — List this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).
- **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. Readings from a logger read out at the dock are accepted after `delivered` if they fall inside the journey (departure − 60 min to arrival + 60 min); a cancelled shipment accepts none. Each logger (`source`) is judged on its own; the assessment reports the worst logger and every logger in temp.by_source, plus unobserved minutes. More than 500 readings, future readings and duplicates are refused or ignored and counted.
- **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, and so does a chip that is not among the shipment's items (even an authentic one: `verify_result` is then uid_not_in_shipment; `chip_verify_result` is the chip's own verdict). `pickup` moves the shipment to in_transit and must come before `delivered` (logged telemetry also counts as departure), and `delivered` closes it. A delivered or cancelled shipment is final: it accepts only `note` events.
- **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.
- **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.
- **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. `grader_check` is match, mismatch, not_found, unavailable (nobody looked), or unverified_identity (the grade agrees but the grader's record does not confirm the card). A chip that has ever been bound to a graded item is refused (use a new chip), and so is a grader cert already bound to another chip — for a re-holdered slab, retire the old binding with record_provenance first. 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.
- **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.
- **record_provenance** — Append an event to a graded item's chain: sold, consigned, vaulted, withdrawn, shipped, received, flagged, retired, 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. `retired` ends the binding (the slab was re-holdered or destroyed) and needs a `note` saying why: the chip stops vouching for any label and the grader cert is freed to be bound to a new chip. A retired item accepts only `note` events.
- **list_graded_items** — List this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).
- **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.
- **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.
- **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.
- **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.
- **get_passport** — Read the PUBLIC view of a published Digital Product Passport hosted by Aeroz, by its GS1 Digital Link (e.g. https://id.aeroz.io/01/09506000134352/21/ABC123) or its passport id (dpp_...). Returns the signed passport fields everyone may see, the version and its date, recall status and the item's links. Fields restricted to repairers, recyclers or authorities are listed as withheld, never shown. This reads the record only: it does NOT prove the physical item in front of you is genuine — use verify_chip with a fresh chip tap for that. A link from another resolver is refused, not fetched. Works without an API key. Passports of sandbox organisations are not public in production.
- **verify_passport_credential** — Check a passport credential (a vc+jwt issued by Aeroz) against Aeroz's published signing keys. Returns valid:true with the issuer, product id, passportVersion and validFrom when the signature checks out and the credential is an Aeroz Digital Product Passport, or valid:false with the reason (including "revoked by the issuer" and "not an Aeroz passport credential"). A valid result means Aeroz issued exactly this content and has not revoked it; it does not mean the passport is the latest version — compare passportVersion with get_passport. Works without an API key.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Aeroz does

The Aeroz MCP server gives an organisation-aware agent tools for authenticating physical units, monitoring compliance, managing shipments, and examining product data. Its core distinction is between a database record and evidence from the item itself. `verify_chip` checks an Aeroz chip UID and its supplied signature, while `check_recall` reads recall status without consuming a chip response.

The server also supports EU Digital Product Passport work. `dpp_readiness` compares a product category with the applicable delegated act and identifies present and missing fields. `get_passport` reads the public view of a published passport, and `verify_passport_credential` validates an Aeroz-issued VC-JWT. These passport operations do not establish that the physical object being inspected is genuine.

For the Industrial & IoT category, Aeroz covers operational workflows as well as product records. Teams can create shipments, record custody handoffs, submit telemetry, plan routes, and inspect exceptions. Additional tools support graded collectible slabs, including chip-to-certification binding and append-only provenance.

## How it works

A chip verification consumes the chip’s one-time answer for that tap. A successful presence proof means the chip answered a fresh SUN challenge; an identity proof means the static signature was issued for that UID, which a copied tag can also carry. A failed signature returns no product data. `signature_unchecked` is not the same as a mismatch, and an unrecognised or unsigned result must not be presented as proof that an item is genuine.

Recall lookup is separate from authentication. It reports whether a UID is known and, when applicable, gives recall details such as reason, severity, date, and identifier. A `null` recall status is unknown, not confirmation that the item is safe. Sandbox keys provide seeded scenarios for authentic, recalled, mismatched, and unregistered chips.

Shipment monitoring evaluates readings against a selected sensitivity profile. Profiles cover cold chain, frozen, ambient, fragile, high-value, and standard movement. Custody events can include a chip tap, and high-value lanes raise findings for unverified handoffs. An open cold-chain excursion requires quarantine on arrival pending quality review.

## Setup and configuration

Aeroz operates against an organisation account and exposes onboarding, agent, findings, usage, and monitoring tools for that account. `list_sandbox_chips` supplies test inputs before physical chips are deployed. Onboarding tools show ownership of open steps; customer-owned manual steps can be completed with `complete_onboarding_step`, while automatically verified steps cannot be self-reported.

Shipment creation requires decimal-degree origin and destination coordinates and a sensitivity profile. Telemetry accepts up to 500 readings per call, and route ranking depends on whether traffic and weather providers are configured for the deployment. PSA certificate cross-checking is available when `PSA_API_TOKEN` is configured.

## Tools and capabilities

The Aeroz MCP server includes tools to:

- Verify chips, resolve identifiers, trace serialized units, and inspect recall status.
- Read passport records, validate passport credentials, and identify missing passport fields.
- List findings, agents, usage summaries, onboarding state, and account-level coverage gaps.
- Create and monitor shipments, record telemetry and custody, and rank routes.
- Bind graded collectibles to chips and append provenance events.
- Ask the organisation’s dedicated agent questions and review prior conversations.

## Limitations and notes

Aeroz outputs readiness and monitoring signals, not legal compliance determinations. `trace_unit`, `chain_readiness`, and passport-readiness results must not be reported as proof of compliance. Public passport retrieval does not authenticate the physical item, and a valid passport credential only proves that Aeroz issued the credential and has not revoked it; it does not prove that the credential is the newest version.

Coverage matters when interpreting findings. An empty findings list does not prove safety if recall sources or other monitoring areas are not covered. Route results are only comparable within one computation, and a time-only ranking must not be described as traffic-aware. Graded-item binding does not grade a card or establish that it was unaltered before sealing.

_Full upstream README: https://allmcps.com/mcp/aeroz/readme_