Aeroz

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.