Aeroz

Name: Aeroz
Author: io.aeroz

MCP serverMCP

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

by io.aerozhomepage ↗v0.2.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"aeroz","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability31/31 checks ok

Endpoints

https://api.aeroz.io/mcpmcp streamable http · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	44 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
7 h ago	mcp initialize	ok	200	86 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
14 h ago	mcp initialize	ok	200	45 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
21 h ago	mcp initialize	ok	200	25 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
28 h ago	mcp initialize	ok	200	43 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
34 h ago	mcp initialize	ok	200	65 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	32 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	25 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	56 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools
3 d ago	mcp initialize	ok	200	150 ms	server aeroz 0.2.0 · protocol 2025-06-18 · 28 tools

Tools observed via MCP handshake

verify_chip — Verify that a physical item is genuine by checking its Aeroz chip UID and cryptographic signature. Use this before trusting any claim about a physical unit — a
check_recall — Check whether a specific unit is subject to an active recall. Returns the recall reason, severity and date when one applies. Use this whenever a unit is about t
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
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_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
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,
list_sandbox_chips — List the seeded sandbox chips for this organisation, including the UID and signature needed to call verify_chip. Sandbox only — use when building or testing an
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
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 w
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
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
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
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
shipment_status — Everything Aeroz holds about one shipment: profile and thresholds, status, items, custody events with their chip verification, the telemetry assessment (min/max
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
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
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
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
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
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
record_provenance — Append an event to a graded item's chain: sold, consigned, vaulted, withdrawn, shipped, received, flagged, note. Events are append-only and, when public, appear
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 ex
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
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.
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

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.aeroz/aeroz

first seen 9 d ago · fetched 2 d agoopen ↗

Field history (6 recent events)

9 d ago · declared · summary → "Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody."
9 d ago · declared · description → "Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody."
9 d ago · declared · publisherName → "io.aeroz"
9 d ago · declared · homepageUrl → "https://aeroz.io"
9 d ago · declared · version → "0.2.0"
9 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from