Agents Index

Aeroz

Online

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

Visit publisherConnectJSON

What it can do: 47 tools

  • verify_chipVerify 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 exist
  • check_recall read-onlyCheck 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, da
  • dpp_readiness read-onlyAssess 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. For batteries (category
  • list_findings read-onlyList 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 read-onlyList 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 read-onlyReturn 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
  • list_sandbox_chips read-onlyList 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
  • onboarding_statusReport 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"
  • onboarding_next_stepReturn 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_stepMark 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 se
  • business_briefThe 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 s
  • ask_agentAsk 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 o
  • agent_conversation read-onlyThe 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_shipmentRegister 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 (s
  • shipment_status read-onlyEverything 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
  • list_shipments read-onlyList this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).
  • log_telemetryRecord 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 as
  • record_custodyRecord 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
  • plan_routeCompute 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. Lo
  • shipment_profiles read-onlyThe 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_itemBind 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 anot
  • graded_item read-onlyA 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, shippe
  • record_provenanceAppend 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
  • list_graded_items read-onlyList this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).
  • my_sectionReturn 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 GS
  • trace_unit read-onlyThe 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 b
  • find_unit read-onlyResolve 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". A
  • chain_readiness read-onlySweep 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"
  • get_passport read-onlyRead 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 field
  • verify_passport_credential read-onlyCheck 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 credentia
  • list_connectors read-onlyThe systems Aeroz can connect to (WMS, ERP, commerce, EPCIS). Each has a tier and `tier_means` in words: `live` moves data today, `credentials` only checks your sign-in, `bridge` needs an on-site agent, `guided` means an
  • list_integrations read-onlyThis company's connected systems, each with its `status` and `status_means`. Only `connected` is proven; `unverified` means stored but not yet proven, which is not the same as working.
  • test_integrationTest one connected system now and return the real result, including the remote server's own error text. Changes its status to what the test proved. Pulls no data.
  • list_webhook_endpoints read-onlyThis company's webhook endpoints: the address (query string hidden), the events each receives, and its health in words. Never shows a signing secret. Needs the `webhooks:read` scope.
  • send_webhook_testSend a signed `ping` to one webhook endpoint now and return the receiver's answer (HTTP status and body). A real request to the customer's address; it is not retried. Needs the `webhooks:write` scope.
  • list_webhook_deliveries read-onlyRecent webhook deliveries, newest first, each with every attempt and the receiver's answer. A `pending` delivery has a `next_attempt_at`: it is being retried, not lost. Needs the `webhooks:read` scope.
  • list_webhook_events read-onlyEvery event Aeroz can send to a webhook, with a description and an example payload (sample values from a fictional company, not real data), how deliveries are signed, and the retry schedule.
  • list_products read-onlyThis company's registered products (archived ones left out). An empty list means recall watch has nothing to match against, not that all is clear.
  • create_productRegister one product, by the same rules as POST /v1/products. Recall watch needs a GTIN, NDC or UPC. Returns the passport gap for its category when there is one; that is a readiness signal, not a legal determination.
  • import_productsAdd or update many products at once, by the same rules as POST /v1/products/import: at most 5,000 rows, each row the fields of create_product. Send `dry_run: true` first: it checks every row and writes nothing. A real im

…and 7 more.

Connect it

Claude Code
claude mcp add --transport http aeroz https://api.aeroz.io/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.aeroz.io/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "aeroz": {
      "url": "https://api.aeroz.io/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "aeroz": {
      "type": "http",
      "url": "https://api.aeroz.io/mcp"
    }
  }
}

Questions

What does Aeroz do?

Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody. It exposes 47 tools to AI assistants.

What tools does Aeroz provide?

47 tools, including verify_chip, check_recall, dpp_readiness, list_findings, list_agents, get_usage, list_sandbox_chips, onboarding_status, onboarding_next_step, complete_onboarding_step, business_brief, ask_agent….

How do I connect Aeroz to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.aeroz.io/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Aeroz require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Aeroz online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Aeroz?

aeroz.io. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Automation & Integrations