← Registry

Security & Testing

aeroz.io

An Aeroz compliance and product-verification MCP server that verifies chip-authenticated physical items, checks recalls, assesses EU Digital Product Passport readiness, and lists compliance findings and agents.

1 endpoint28 known toolsFirst detected October 15, 2026Last detected October 20, 2026

ENDPOINT 1

https://api.aeroz.io/mcp

No auth detected

MCP server metadata

Name
aeroz
Version
0.2.0
Capabilities
tools
Server instructions

You are connected to Aeroz without an API key. You can list tools; calling one needs a key. Create a free sandbox key with POST https://api.aeroz.io/v1/signup {"company","email","sector"} and reconnect with Authorization: Bearer <key>.

Known tools 28

verify_chip

Verify that a physical item is genuine by checking its Aeroz chip UID and cryptographic signature.

Inferred read-only
check_recall

Check whether a specific unit is subject to an active recall.

Inferred read-only
dpp_readiness

Assess how ready a product category is for an EU Digital Product Passport, against the delegated act that applies to it.

Inferred read-only
list_findings

List findings raised by the Aeroz compliance agents watching this organisation — recall hits, DPP data gaps, regulatory changes, dwell anomalies, and clone detections.

Inferred read-only
list_agents

List the Aeroz compliance agents available to this organisation and which are currently enabled.

Inferred read-only
get_usage

Return this organisation's Aeroz verification volume and outcome breakdown over a recent period.

Inferred read-only
list_sandbox_chips

List the seeded sandbox chips for this organisation, including the UID and signature needed to call verify_chip.

Inferred read-only
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 side owns it.

Inferred read-only
onboarding_next_step

Return only the single most important next action and how to complete it.

Inferred read-only
complete_onboarding_step

Mark a manual onboarding step complete on behalf of this organisation.

Inferred read-only
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, onboarding state, open findings, and — importantly — which recall sources are NOT being monitored.

Inferred read-only
ask_agent

Ask this organisation's dedicated Aeroz agent a question in plain language and get a grounded answer.

Inferred read-only
agent_conversation

The recent conversation between this organisation and its Aeroz agent, across the dashboard, MCP and email.

Potential side effects
create_shipment

Register a shipment of physical items under a sensitivity profile so Aeroz can watch it in transit.

Inferred read-only
shipment_status

Everything 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 range, peak shock, whether an excursion is open), the ranked routes, and open findings.

Inferred read-only
list_shipments

List this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).

Inferred read-only
log_telemetry

Record sensor readings for a shipment — position, temperature, humidity, shock, tilt, light, battery — up to 500 per call.

Inferred read-only
record_custody

Record a custody event on a shipment: pickup, checkpoint, handoff, delivered, exception or note.

Inferred read-only
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 way against the lane's ceiling, and rain, snow or gusts.

Inferred read-only
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 this deployment.

Inferred read-only
bind_graded_item

Bind an Aeroz chip to a graded collectible slab (PSA, CGC, SGC, BGS, TAG).

Inferred read-only
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 full provenance chain (sealed, sold, consigned, vaulted, shipped, verified…).

Inferred read-only
record_provenance

Append an event to a graded item's chain: sold, consigned, vaulted, withdrawn, shipped, received, flagged, note.

Inferred read-only
list_graded_items

List this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).

Inferred read-only
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 exactly which fields are missing, the identifier audit, the GS1 route, monitoring coverage, integration readiness, and the pre-filled audit scope.

Inferred read-only
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 regulation makes of it.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aeroz]
url = "https://api.aeroz.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "aeroz": {
      "type": "http",
      "url": "https://api.aeroz.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: aeroz
Remote MCP URL: https://api.aeroz.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "aeroz": {
      "url": "https://api.aeroz.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "aeroz": {
      "type": "http",
      "url": "https://api.aeroz.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "aeroz",
  "transport": "streamable-http",
  "url": "https://api.aeroz.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for aeroz.io was fetched 2026-10-16T04:58:47.841Z.

Trust status Trusted

aeroz.io is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.