Aeroz

1. Tool surface changed

   2026-10-17 18:26 UTC · 6 d ago

   Removed "get_passport" and "verify_passport_credential"; changed the definition of "agent_conversation", "ask_agent", "bind_graded_item" and 25 more (30 tools before, 28 now)

   agent_conversationchanged

   title

   before
   Agent conversation

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Agent conversation"}

   after
   —

   ask_agentchanged

   title

   before
   Ask the Aeroz agent

   after
   —

   description

    ⟨107 unchanged words⟩ 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). Itnever sends nothing outside Aerozanything andor changes no product, shipment or passportthe data.account.

   36 words differ · removed · added

   inputSchema

    ⟨3 unchanged words⟩ ":"The question, as the person asked it (at most 2000 characters).

   bind_graded_itemchanged

   title

   before
   Bind a graded item

   after
   —

   description

    ⟨68 unchanged words⟩ 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  ⟨25 unchanged words⟩ 

   75 words differ · removed · added

   inputSchema

   {"properties":{"back_image_url":{"maxLength":500,"type":"string"},"card_number":{"maxLength":32,"type":"string"},"category":{"enum":["trading_card","coin","comic","memorabilia","other"],"maxLength":40,"type":"string"},"cert_number":{"maxLength":64,"

   business_briefchanged

   title

   before
   Business brief

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":false,"title":"Business brief"}

   after
   —

   chain_readinesschanged

   title

   before
   Chain readiness

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Chain readiness"}

   after
   —

   check_recallchanged

   title

   before
   Check a recall

   after
   —

   description

   Check whether a specific unit is subject to an active recall, from the register: reads only, verifies no signature and spends no chip answer.recall. Returns known (on the register), recalled, and the recall reason, severity, date and iddate 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 this 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).

   103 words differ · removed · added

   complete_onboarding_stepchanged

   title

   before
   Complete an onboarding step

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":false,"title":"Complete an onboarding step"}

   after
   —

   create_shipmentchanged

   title

   before
   Create a shipment

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":false,"openWorldHint":false,"readOnlyHint":false,"title":"Create a shipment"}

   after
   —

   dpp_readinesschanged

   title

   before
   Passport readiness

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Passport readiness"}

   after
   —

   find_unitchanged

   title

   before
   Find a unit

   after
   —

   inputSchema

    ⟨9 unchanged words⟩ :"Chip UID read from a tap.","maxLength":64,"type":"string"},"upi":{"description" ⟨14 unchanged words⟩ 

   6 words differ · removed · added

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Find a unit"}

   after
   —

   get_usagechanged

   title

   before
   Usage

   after
   —

   description

    ⟨17 unchanged words⟩  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.

   53 words differ · removed · added

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Usage"}

   after
   —

   graded_itemchanged

   title

   before
   Graded item

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Graded item"}

   after
   —

   list_agentschanged

   title

   before
   List agents

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"List agents"}

   after
   —

   list_findingschanged

   title

   before
   List compliance findings

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"List compliance findings"}

   after
   —

   list_graded_itemschanged

   title

   before
   List graded items

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"List graded items"}

   after
   —

   list_sandbox_chipschanged

   title

   before
   List sandbox chips

   after
   —

   description

   List the seeded sandbox chips for this organisation, withincluding the UID and signature to passneeded 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 thecall register).verify_chip. Sandbox only — use when building or testing ⟨6 unchanged words⟩ 

   39 words differ · removed · added

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"List sandbox chips"}

   
   —

   list_shipmentschanged

   title

   before
   List shipments

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"List shipments"}

   after
   —

   log_telemetrychanged

   title

   before
   Log telemetry

   after
   —

   description

    ⟨42 unchanged words⟩  `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.

   76 words differ · removed · added

   annotations

   before
   {"destructiveHint":false,"idempotentHint":false,"openWorldHint":false,"readOnlyHint":false,"title":"Log telemetry"}

   after
   —

   my_sectionchanged

   title

   before
   My section

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":false,"title":"My section"}

   after
   —

   onboarding_next_stepchanged

   title

   before
   Next onboarding step

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":false,"title":"Next onboarding step"}

   after
   —

   onboarding_statuschanged

   title

   before
   Onboarding status

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":false,"title":"Onboarding status"}

   after
   —

   plan_routechanged

   title

   before
   Plan a route

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":false,"openWorldHint":true,"readOnlyHint":false,"title":"Plan a route"}

   after
   —

   record_custodychanged

   title

   before
   Record custody

   after
   —

   description

    ⟨45 unchanged words⟩ 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).finding. `pickup` moves the shipment to in_transit and must come before `delivered` (logged telemetry also counts as departure), andin_transit; `delivered` closes it. A delivered or cancelled shipment is final: it accepts only `note` events.

   63 words differ · removed · added

   annotations

   before
   {"destructiveHint":false,"idempotentHint":false,"openWorldHint":false,"readOnlyHint":false,"title":"Record custody"}

   after
   —

   record_provenancechanged

   title

   before
   Record provenance

   after
   —

   description

    ⟨10 unchanged words⟩  vaulted, withdrawn, shipped, received, flagged, retired, note. Events are append-only and, when public,  ⟨5 unchanged words⟩ page. `flagged` marks the item and needs a `note`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.

   50 words differ · removed · added

   inputSchema

   {"properties":{"actor":{"maxLength":120,"type":"string"},"item_id":{"type" ⟨6 unchanged words⟩ withdrawn","shipped","received","flagged","retired","note"],"type":"string"},"location":{"

   shipment_profileschanged

   title

   before
   Shipment profiles

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Shipment profiles"}

   after
   —

   shipment_statuschanged

   title

   before
   Shipment status

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Shipment status"}

   after
   —

   trace_unitchanged

   title

   before
   Trace a unit

   after
   —

   annotations

   before
   {"destructiveHint":false,"idempotentHint":true,"openWorldHint":false,"readOnlyHint":true,"title":"Trace a unit"}

   after
   —

   verify_chipchanged

   title

   before
   Verify a chip

   after
   —

   description

   Verify that a physical item is genuine by checking its Aeroz chip: the UID plus whatever signature the tap carried. Same answer asand GETcryptographic /v1/verify.signature. Use this before trusting any claim about a ⟨15 unchanged words⟩ 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.Returns 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 

   get_passportremoved

   Read a product 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 wi…

   verify_passport_credentialremoved

   Verify a 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.

2. TLS

   2026-10-16 17:27 UTC · 7 d ago

   Certificate recorded, valid to 2026-11-28

3. Authorization

   2026-10-16 17:27 UTC · 7 d ago

   Authorization not required

4. Status

   2026-10-15 13:23 UTC · 9 d ago

   Unknown → Live

5. Tool surface

   2026-10-15 13:23 UTC · 9 d ago

   First tool surface recorded: 30 tools (server version 0.2.0)

6. Endpoint

   2026-10-15 13:18 UTC · 9 d ago

   https://api.aeroz.io/mcp (mcp_streamable_http) — from mcp_registry, with the record

Showing the latest 6 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed