# Aeroz MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.aeroz%2Faeroz
Registry id: `mcp-registry/io.aeroz/aeroz`
Status: live (checked 2026-11-22T16:39:24.331Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 897
- Outages (90 days): 0

## Install

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

Claude Code:

```sh
claude mcp add --transport http aeroz-mcp-server https://api.aeroz.io/mcp
```

## Tools (47)

- `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 answer
- `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 thei
- `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 th
- `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, onboard
- `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 
- `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 
- `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 w
- `create_product`: Register 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
- `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), fro
- `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
- `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.
- `get_import_template_columns`: The columns import_products reads, in the template's order, with the template's sample rows (a fictional company's products, not real data), the row limit and t
- `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 
- `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,
- `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 ful
- `import_products`: Add 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: tr
- `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 wor
- `list_ai_systems`: This company's register of AI systems: each one's purpose, role under the EU AI Act, risk class (the company's own assessment), how a person can override it, an
- `list_connectors`: The 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
- `list_findings`: List findings raised by the Aeroz compliance agents watching this organisation — recall hits, DPP data gaps, regulatory changes, dwell anomalies, and clone dete
- `list_graded_items`: List this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).
- `list_integrations`: This company's connected systems, each with its `status` and `status_means`. Only `connected` is proven; `unverified` means stored but not yet proven, which is 
- `list_products`: This company's registered products (archived ones left out). An empty list means recall watch has nothing to match against, not that all is clear.
- `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_mismatc
- `list_shipments`: List this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).
- `list_webhook_deliveries`: Recent 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, n
- `list_webhook_endpoints`: This 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 
- `list_webhook_events`: Every 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 s
- `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 
- `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 ex
- `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.
- `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 si
- `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
- `record_ai_decision`: Append a decision (or an incident) to an AI system's signed, append-only record, by the rules of POST /v1/ai/systems/{id}/records. Send the input and output tex
- `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 A
- `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 publi
- `register_ai_system`: Register an AI system, by the rules of POST /v1/ai/systems. Name and purpose are fixed once registered. A high-risk system with no `oversight` is accepted with 
- `review_ai_decision`: Record a person's review of an AI decision (approved, overridden or rejected; overriding or rejecting needs a `note`), by the rules of POST /v1/ai/records/{id}/
- `search`: Search this company's records the way the dashboard search bar does: products (name, SKU, GTIN, NDC), lots, units (chip ID, serial), tags (UID, EPC), shipments 
- `send_webhook_test`: Send 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 re
- `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
- `shipment_status`: Everything Aeroz holds about one shipment: profile and thresholds, status, items, custody events with their chip verification, the telemetry assessment (min/max
- `test_integration`: Test 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 dat
- `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 
- `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 abo
- `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 a
- `where_is`: Where a product's or a lot's units are, by last known place: sites, partners, scans and shipments in transit, each with how the place is known. Units with no re

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
