Aeroz MCP server
io.aeroz/aerozaeroz.iostreamable-httpv0.2.0Scanned
Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody.
47 tools: 4 can delete or cancel things, 1 do something that can't be undone, 25 change things and 17 only read.
- Reads private data · 1
- Reads text others write · 8
- Can send data out · 1
- 10 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Aeroz MCP server can do
The Aeroz MCP server is published by aeroz.io, a domain the MCP Registry verified. It has 47 tools. It can delete or cancel things (4 tools: list_ai_systems, register_ai_system, record_ai_decision and review_ai_decision), do things that cannot be undone, such as sending, paying or publishing (send_webhook_test) and create or change data (25 tools: verify_chip, check_recall, dpp_readiness, onboarding_status and 21 more). 17 tools only read.
1 tool reads private data (my_section); 8 tools bring in text other people can write (plan_route, find_unit, test_integration and 5 more); 1 tool can send data out of your system (send_webhook_test). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 10 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
47 tools
Deletes or cancels 4Claude Code: deny
list_ai_systemsThis 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, and how many decisions…Reads text others write1 finding
Why it is in this group
- The name "list_ai_systems" says "list": a word for reading.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "list_ai_systems" destructive (destructiveHint: true), and its name says "list", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "list_ai_systems" says "list": a word for reading.
Description, as the server wrote it 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, and how many decisions are on record. Use it to find the system_id to log against.
Annotations the server declares
- title: list_ai_systems
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
record_ai_decisionAppend a decision (or an incident) to an AI system's signed, append-only record, by the rules of POST /v1/ai/systems/{id}/records.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 text or their SHA-256: only the hash is kept, never the text. Nothing recorded can be edited or removed, so record what actually happened, not a guess.
Annotations the server declares
- title: record_ai_decision
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
register_ai_systemRegister an AI system, by the rules of POST /v1/ai/systems.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 a warning (AI Act Art. 14). Classifying the system is the company's call; do not choose a risk class the user has not given you: leave it unassessed.
Annotations the server declares
- title: register_ai_system
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
review_ai_decisionRecord 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}/review.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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}/review. Only call this with the decision a person actually made: never approve on your own judgement, because the record says a human reviewed it.
Annotations the server declares
- title: review_ai_decision
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Can't be undone 1Claude Code: ask
send_webhook_testSend a signed `ping` to one webhook endpoint now and return the receiver's answer (HTTP status and body).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_webhook_test" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_webhook_test" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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 retried. Needs the `webhooks:write` scope.
Annotations the server declares
- title: Send a test webhook
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 25Claude Code: ask
agent_conversationThe recent conversation between this organisation and its Aeroz agent, across the dashboard, MCP and email.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 answered before asking again.
Annotations the server declares
- title: Agent conversation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ask_agentAsk this organisation's dedicated Aeroz agent a question in plain language and get a grounded answer.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 their account manager: "what do we still need to do", "when is our deadline", "what is Aeroz waiting on", "what is not being monitored", "how do we go live". It also looks up lots, units, holds and shipments ("where is lot X", "which units of Y are on hold", "what shipped to Z last week") in this company's own records, within this key's read scopes, and answers "how do I…" and compliance questions from Aeroz's help topics. The answer carries `grounded`: `records` means it was read from the company's records (the records are in `chips`); `knowledge` means it came from an Aeroz help topic (sections in `citations`; compliance answers are readiness signals, not legal determinations); `computed` means it was read directly from the account's own data; `model` means a model composed it from that data and every date and figure was checked against it; `declined` means the agent does not hold what the question needs and said so — relay that 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). It sends nothing outside Aeroz and changes no product, shipment or passport data.
Annotations the server declares
- title: Ask the Aeroz agent
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
bind_graded_itemBind an Aeroz chip to a graded collectible slab (PSA, CGC, SGC, BGS, TAG).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 the chip vouches for exactly this label: a label moved to another holder, or a cert reprinted on a copy, shows as "binding broken" on a buyer's tap. For PSA, the cert is cross-checked against PSA's own record when 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 the slab's QR. This does NOT grade the card and does not claim the card was unaltered before sealing — never present it as either.
Annotations the server declares
- title: Bind a graded item
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
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 find…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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. Use this to orient before answering anything about the account. Never present an empty findings list as evidence of safety without also reporting coverage_gaps.
Annotations the server declares
- title: Business brief
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
chain_readinessSweep this organisation's units and report which regulatory checks are failing across the portfolio, how many units each affects, and examples to open.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 the tool for "which of my units have a broken custody chain", "what is failing right now", "what will not pass on 18 February" and "how are we doing overall". Counts are exact for the units swept; the response says when it hit its cap rather than implying it saw everything. An empty findings list means nothing failed among the units swept — it does not mean the organisation is compliant.
Annotations the server declares
- title: Chain readiness
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_recallCheck whether a specific unit is subject to an active recall, from the register: reads only, verifies no signature and spends no chip answer.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 the register), recalled, and the recall reason, severity, date and id 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 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).
Annotations the server declares
- title: Check a recall
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
complete_onboarding_stepMark a manual onboarding step complete on behalf of this organisation.No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
Description, as the server wrote it 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 way; an automatically verified step will refuse, because a self-report that contradicts the platform data is worse than no report. Pass the step key from onboarding_status.
Annotations the server declares
- title: Complete an onboarding step
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_productRegister one product, by the same rules as POST /v1/products.No findings
Why it is in this group
- The name "create_product" says "create": a word for a change.
Description, as the server wrote it 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; that is a readiness signal, not a legal determination.
Annotations the server declares
- title: Create a product
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_shipmentRegister a shipment of physical items under a sensitivity profile so Aeroz can watch it in transit.No findings
Why it is in this group
- The name "create_shipment" says "create": a word for a change.
Description, as the server wrote it 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), frozen (≤ −15 °C), ambient_crt (15–30 °C, MKT ≤ 25), fragile (shock, tilt), high_value (light = container opened, dwell, chip-verified custody at every handoff), standard (movement only). Origin and destination need decimal-degree coordinates. Items may carry a chip uid, GTIN, lot and serial. Returns the shipment id and the thresholds that will judge it.
Annotations the server declares
- title: Create a shipment
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
dpp_readinessAssess how ready a product category is for an EU Digital Product Passport, against the delegated act that applies to it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 are present, and which are missing. For batteries (category "batteries", or "lmt" / "ev" / "industrial" / "stationary") the assessment is against the Commission's 71 numbered data points: score, missing, not-required-yet, awaiting first reading and go_live_ready per passport; pass unit_id for one battery passport. IMPORTANT: this is a readiness signal, not a legal compliance determination — never report its output as confirmation that a product is compliant.
Annotations the server declares
- title: Passport readiness
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
graded_itemA 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 (…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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…). Use for "is this slab the one that was sealed", "where has it been", "has anyone tried to pass off a copy". Report what this proves AND what it does not.
Annotations the server declares
- title: Graded item
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- The name "import_products" says "import": a word for a change.
Description, as the server wrote it 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: true` first: it checks every row and writes nothing. A real import writes nothing while any row has a problem. Each row comes back as create, update, unchanged or conflict.
Annotations the server declares
- title: Import products
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
log_telemetryRecord sensor readings for a shipment — position, temperature, humidity, shock, tilt, light, battery — up to 500 per call.1 finding
Why it is in this group
- The name "log_telemetry" says "log": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "log_telemetry" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "log_telemetry" says "log": a word for reading.
Description, as the server wrote it Record 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 assessment and any findings raised. A shipment in `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.
Annotations the server declares
- title: Log telemetry
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
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 a…Reads private data1 finding
Why it is in this group
- The description's first verb is "return": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "return" and "calendar": it reads calendars.
Findings
- Warn
The server marks "my_section" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "return": a word for reading.
Description, as the server wrote it 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. Each block carries a confidence — `computed` is derived from this account's own data and needs no review; `sourced` and `drafted` came from outside the platform or involved judgement and are cited. Use this to answer almost any question about what this business needs to do. Report a block's confidence when you rely on it, and never present a `drafted` block as settled.
Annotations the server declares
- title: My section
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
onboarding_next_stepReturn only the single most important next action and how to complete it.1 finding
Why it is in this group
- The description's first verb is "return": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "onboarding_next_step" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Next onboarding step
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.1 finding
Why it is in this group
- The name "onboarding_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "onboarding_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "onboarding_status" says "status": a word for reading.
Description, as the server wrote it 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. Use this to answer "what do we still need to do", "why are we not live yet", or "what is Aeroz waiting on". Steps marked side="aeroz" are Aeroz's obligation, not the customer's — say so plainly rather than presenting them as homework.
Annotations the server declares
- title: Onboarding status
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 lan…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Lower score is better and only comparable within one computation. The best route is marked chosen. The response says plainly when routing or weather data was unavailable and the ranking is time-only — relay that; a straight-line estimate is not a traffic-aware route.
Annotations the server declares
- title: Plan a route
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
record_custodyRecord a custody event on a shipment: pickup, checkpoint, handoff, delivered, exception or note.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 Aeroz verifies it on the spot, turning a signature on a form into proof of presence. On a high_value lane 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). `pickup` moves the shipment to in_transit and must come before `delivered` (logged telemetry also counts as departure), and `delivered` closes it. A delivered or cancelled shipment is final: it accepts only `note` events.
Annotations the server declares
- title: Record custody
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
record_provenanceAppend an event to a graded item's chain: sold, consigned, vaulted, withdrawn, shipped, received, flagged, retired, note.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Append 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 and needs a `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.
Annotations the server declares
- title: Record provenance
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
shipment_profilesThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Shipment profiles
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
test_integrationTest one connected system now and return the real result, including the remote server's own error text.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 data.
Annotations the server declares
- title: Test an integration
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
trace_unitThe 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 …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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. Use this to answer "where has this been", "who handled it", "is its record trustworthy" and "does this unit pass DSCSA / the EU passport rules". Every failing check cites the clause it enforces — quote the clause, not just the verdict. IMPORTANT: verdicts are readiness signals, never a legal compliance determination, and the response says so. Never report one as confirmation that a product is compliant.
Annotations the server declares
- title: Trace a unit
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_chipVerify a physical item by its Aeroz chip: the UID plus whatever signature the tap carried.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 about a physical unit — a database record proves a record exists, not that the object in 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. 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 a mismatch). A failed signature returns NO product data. Each call records the tap and spends the chip's one-time answer, so pass each SUN tap once. A sandbox key answers its seeded sandbox chips as fixtures (mode "sandbox" with a _warning) and any other UID from the register (mode "sandbox", register:true), so a sandbox company can check the test tags it minted.
Annotations the server declares
- title: Verify a chip
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
verify_passport_credentialCheck a passport credential (a vc+jwt issued by Aeroz) against Aeroz's published signing keys.4 findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The title mentions "credential".
What this check looks forMatched text
title: "Verify a passport credential"
- Info
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Verify a passport credential"
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Check a passport credential (a vc+jwt issued by Aeroz) against Aero..."
- Info
The input schema at properties.jwt.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.jwt.description: "The compact vc+jwt credential."
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify a passport credential
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
where_isWhere 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 recorded place are counted and listed, never placed. Give `product` (a product id), `lot`, or both.
Annotations the server declares
- title: Where are these units
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 17Show 17 read-only tools
find_unitResolve 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.Reads text others writeNo findings
Why it is in this group
- The name "find_unit" says "find": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "resolve" and "uri": it reads web pages, which anyone can write.
Description, as the server wrote it 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. This is the tool for "what is this thing in front of me". An identifier that resolves to nothing is NOT the same as one that fails verification: the first means we have never seen it, the second means we have and it did not check out. Report them differently.
Annotations the server declares
- title: Find a unit
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_import_template_columnsThe 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 the rule for matching…No findings
Why it is in this group
- The name "get_import_template_columns" says "get": a word for reading.
Description, as the server wrote it 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 the rule for matching rows to existing products.
Annotations the server declares
- title: Import template columns
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_passportRead the PUBLIC view of a published Digital Product Passport hosted by Aeroz, by its GS1 Digital Link (e.g.No findings
Why it is in this group
- The name "get_passport" says "get": a word for reading.
Description, as the server wrote it 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 legitimate-interest roles (repairers, recyclers, purchasers and others, per the battery access policy) 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 without an API key. Passports of sandbox organisations are not public in production.
Annotations the server declares
- title: Read a product passport
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_usageReturn this organisation's Aeroz verification volume and outcome breakdown over a recent period.No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it Return 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 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.
Annotations the server declares
- title: Usage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_agentsList the Aeroz compliance agents available to this organisation and which are currently enabled.No findings
Why it is in this group
- The name "list_agents" says "list": a word for reading.
Description, as the server wrote it 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 worth enabling.
Annotations the server declares
- title: List agents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_connectorsThe systems Aeroz can connect to (WMS, ERP, commerce, EPCIS).1 finding
Why it is in this group
- The name "list_connectors" says "list": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ns` in words: `live` moves data today, `credentials` only checks your sign-in, `bridge` nee..."
Description, as the server wrote it 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 sign-in, `bridge` needs an on-site agent, `guided` means an Aeroz engineer finishes the hookup. Do not describe a guided connector as automatic.
Annotations the server declares
- title: List connectors
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_findingsList findings raised by the Aeroz compliance agents watching this organisation — recall hits, DPP data gaps, regulatory changes, dwell anomalies, and clone detections.No findings
Why it is in this group
- The name "list_findings" says "list": a word for reading.
Description, as the server wrote it List 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".
Annotations the server declares
- title: List compliance findings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_graded_itemsList this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).No findings
Why it is in this group
- The name "list_graded_items" says "list": a word for reading.
Description, as the server wrote it List this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).
Annotations the server declares
- title: List graded items
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_integrationsThis company's connected systems, each with its `status` and `status_means`.No findings
Why it is in this group
- The name "list_integrations" says "list": a word for reading.
Description, as the server wrote it 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 not the same as working.
Annotations the server declares
- title: List integrations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_productsThis company's registered products (archived ones left out).No findings
Why it is in this group
- The name "list_products" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List products
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_sandbox_chipsList 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 del…No findings
Why it is in this group
- The name "list_sandbox_chips" says "list": a word for reading.
Description, as the server wrote it List 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 (a UID that is not on the register). Sandbox only — use when building or testing an integration before physical chips ship.
Annotations the server declares
- title: List sandbox chips
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_shipmentsList this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).No findings
Why it is in this group
- The name "list_shipments" says "list": a word for reading.
Description, as the server wrote it List this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).
Annotations the server declares
- title: List shipments
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_webhook_deliveriesRecent webhook deliveries, newest first, each with every attempt and the receiver's answer.No findings
Why it is in this group
- The name "list_webhook_deliveries" says "list": a word for reading.
Description, as the server wrote it 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, not lost. Needs the `webhooks:read` scope.
Annotations the server declares
- title: List webhook deliveries
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_webhook_endpointsThis company's webhook endpoints: the address (query string hidden), the events each receives, and its health in words.No findings
Why it is in this group
- The name "list_webhook_endpoints" says "list": a word for reading.
Description, as the server wrote it 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 `webhooks:read` scope.
Annotations the server declares
- title: List webhook endpoints
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_webhook_eventsEvery 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…No findings
Why it is in this group
- The name "list_webhook_events" says "list": a word for reading.
Description, as the server wrote it 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 signed, and the retry schedule.
Annotations the server declares
- title: List webhook events
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
searchSearch 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 (reference, carrier,…No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it 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 (reference, carrier, places), holds and cases, partners (name, GLN), locations, recalls, integrations and webhooks by name, plus Aeroz help topics. Paste an identifier as-is — a GTIN, NDC, GLN, lot, chip ID, GS1 Digital Link, element string or EPC URN is parsed and exact matches come first (`match: identifier`). Each area needs its own read scope; areas this key cannot read are listed in `skipped` — say so rather than reading an empty group as "none". Each hit has `href`, the dashboard screen it opens. To answer a question, use ask_agent.
Annotations the server declares
- title: Search records and help
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
shipment_statusEverything Aeroz holds about one shipment: profile and thresholds, status, items, custody events with their chip verification, the telemetry assessment (min/max/mean temperature, m…No findings
Why it is in this group
- The name "shipment_status" says "status": a word for reading.
Description, as the server wrote it 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. Use for "where is it", "is the cold chain intact", "was it ever opened". An open excursion on a cold-chain lane means the load must be quarantined on arrival pending QA — say so.
Annotations the server declares
- title: Shipment status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__aeroz__send_webhook_test"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:55 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 30
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 30 tools that change things (4 destructive, 1 irreversible, 25 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.aeroz.io/mcp: tools/list returned 47 tools to an anonymous client, including list_ai_systems (destructive), register_ai_system (destructive), record_ai_decision (destructive), review_ai_decision (destructive), send_webhook_test (irreversible) and 25 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 26 to 30
- Oct 29, 2026
- Tools that change things, listed without credentials: 16 to 26
Findings
Matches of fixed checks, with the text they matched.
The server marks "onboarding_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "onboarding_status" says "status": a word for reading.
The server marks "onboarding_next_step" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "return": a word for reading.
- Warnlog_telemetry
The server marks "log_telemetry" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "log_telemetry" says "log": a word for reading.
- Warnmy_section
The server marks "my_section" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "return": a word for reading.
- Warnlist_ai_systems
The server marks "list_ai_systems" destructive (destructiveHint: true), and its name says "list", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "list_ai_systems" says "list": a word for reading.
The title mentions "credential".
What this check looks forMatched text
title: "Verify a passport credential"
Show 4 more findingsShow fewer
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Verify a passport credential"
The description mentions "credential".
What this check looks forMatched text
description: "Check a passport credential (a vc+jwt issued by Aeroz) against Aero..."
The input schema at properties.jwt.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.jwt.description: "The compact vc+jwt credential."
- Infolist_connectors
The description mentions "credentials".
What this check looks forMatched text
description: "...ns` in words: `live` moves data today, `credentials` only checks your sign-in, `bridge` nee..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 added, 4 changed.+4 added~4 changedView diff
- Added:list_ai_systemsDeletes or cancels
- Added:record_ai_decisionDeletes or cancels
- Added:register_ai_systemDeletes or cancels
- Added:review_ai_decisionDeletes or cancels
- Changed:chain_readinessChanges thingsinputSchema
- Changed:dpp_readinessChanges thingsdescriptioninputSchema
- Changed:get_passportOnly readsdescription
- Changed:trace_unitChanges thingsinputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 26 -> 30.View diff
- Tools that change things, listed without credentials: 26 to 30
Tools15 added, 28 changed.+15 added~28 changedView diff
- Added:create_productChanges things
- Added:get_import_template_columnsOnly reads
- Added:get_passportOnly reads
- Added:import_productsChanges things
- Added:list_connectorsOnly reads
- Added:list_integrationsOnly reads
- Added:list_productsOnly reads
- Added:list_webhook_deliveriesOnly reads
- Added:list_webhook_endpointsOnly reads
- Added:list_webhook_eventsOnly reads
- Added:searchOnly reads
- Added:send_webhook_testCan't be undone
- Added:test_integrationChanges things
- Added:verify_passport_credentialChanges things
- Added:where_isChanges things
- Changed:agent_conversationChanges thingstitleannotations
- Changed:ask_agentChanges thingstitledescriptioninputSchemaannotations
- Changed:bind_graded_itemChanges thingstitledescriptioninputSchemaannotations
- Changed:business_briefChanges thingstitleannotations
- Changed:chain_readinessChanges thingstitleannotations
- Changed:check_recallChanges thingstitledescriptionannotations
- Changed:complete_onboarding_stepChanges thingstitleannotations
- Changed:create_shipmentChanges thingstitleannotations
- Changed:dpp_readinessChanges thingstitleannotations
- Changed:find_unitOnly readstitleinputSchemaannotations
- Changed:get_usageOnly readstitledescriptionannotations
- Changed:graded_itemChanges thingstitleannotations
- Changed:list_agentsOnly readstitleannotations
- Changed:list_findingsOnly readstitleannotations
- Changed:list_graded_itemsOnly readstitleannotations
- Changed:list_sandbox_chipsOnly readstitledescriptionannotations
- Changed:list_shipmentsOnly readstitleannotations
- Changed:log_telemetryChanges thingstitledescriptionannotations
- Changed:my_sectionChanges thingstitleannotations
- Changed:onboarding_next_stepChanges thingstitleannotations
- Changed:onboarding_statusChanges thingstitleannotations
- Changed:plan_routeChanges thingstitleannotations
- Changed:record_custodyChanges thingstitledescriptionannotations
- Changed:record_provenanceChanges thingstitledescriptioninputSchemaannotations
- Changed:shipment_profilesChanges thingstitleannotations
- Changed:shipment_statusOnly readstitleannotations
- Changed:trace_unitChanges thingstitleannotations
- Changed:verify_chipChanges thingstitledescriptioninputSchemaannotations
PostureRemote posture changed. Tools that change things, listed without credentials: 16 -> 26.View diff
- Tools that change things, listed without credentials: 16 to 26
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http aeroz https://api.aeroz.io/mcpclaude mcp add --transport http aeroz https://api.aeroz.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__aeroz__list_findings",
"mcp__aeroz__list_agents",
"mcp__aeroz__get_usage",
"mcp__aeroz__list_sandbox_chips",
"mcp__aeroz__shipment_status",
"mcp__aeroz__list_shipments",
"mcp__aeroz__list_graded_items",
"mcp__aeroz__find_unit",
"mcp__aeroz__get_passport",
"mcp__aeroz__list_connectors",
"mcp__aeroz__list_integrations",
"mcp__aeroz__list_webhook_endpoints",
"mcp__aeroz__list_webhook_deliveries",
"mcp__aeroz__list_webhook_events",
"mcp__aeroz__list_products",
"mcp__aeroz__get_import_template_columns",
"mcp__aeroz__search"
],
"ask": [
"mcp__aeroz__verify_chip",
"mcp__aeroz__check_recall",
"mcp__aeroz__dpp_readiness",
"mcp__aeroz__onboarding_status",
"mcp__aeroz__onboarding_next_step",
"mcp__aeroz__complete_onboarding_step",
"mcp__aeroz__business_brief",
"mcp__aeroz__ask_agent",
"mcp__aeroz__agent_conversation",
"mcp__aeroz__create_shipment",
"mcp__aeroz__log_telemetry",
"mcp__aeroz__record_custody",
"mcp__aeroz__plan_route",
"mcp__aeroz__shipment_profiles",
"mcp__aeroz__bind_graded_item",
"mcp__aeroz__graded_item",
"mcp__aeroz__record_provenance",
"mcp__aeroz__my_section",
"mcp__aeroz__trace_unit",
"mcp__aeroz__chain_readiness",
"mcp__aeroz__verify_passport_credential",
"mcp__aeroz__test_integration",
"mcp__aeroz__send_webhook_test",
"mcp__aeroz__create_product",
"mcp__aeroz__import_products",
"mcp__aeroz__where_is"
],
"deny": [
"mcp__aeroz__list_ai_systems",
"mcp__aeroz__register_ai_system",
"mcp__aeroz__record_ai_decision",
"mcp__aeroz__review_ai_decision"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as aeroz. Review it before you use it.
Capability tags behind 9 rules
- mcp__aeroz__plan_route untrusted-input
- mcp__aeroz__my_section private-data
- mcp__aeroz__find_unit untrusted-input
- mcp__aeroz__test_integration untrusted-input
- mcp__aeroz__send_webhook_test untrusted-input, outbound
- mcp__aeroz__list_ai_systems untrusted-input
- mcp__aeroz__register_ai_system untrusted-input
- mcp__aeroz__record_ai_decision untrusted-input
- mcp__aeroz__review_ai_decision untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.aeroz/aeroz/verify?hash=410d978bbe6771f851c118ad4fa4abc85c804fc7b046bfcf16248b1c2ff0f06e" | jq -e '.changed == false'Pinned hash 410d978bbe67, from Nov 15, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.aeroz/aeroz/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.aeroz/aeroz)Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.
Aeroz MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Aeroz MCP server safe?
- No scan can promise that. What its definitions show: 47 tools, 30 of which can change, send or delete something, and 10 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Aeroz MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: list_ai_systems, register_ai_system, record_ai_decision and review_ai_decision.
Can the Aeroz MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: send_webhook_test.
What tools does the Aeroz MCP server have?
- 47 tools: 4 destructive, 1 irreversible, 25 write, 17 read. list_ai_systems, register_ai_system, record_ai_decision, review_ai_decision, send_webhook_test, verify_chip, check_recall, dpp_readiness and 39 more.
Does the Aeroz MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Aeroz MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_webhook_test.
Has the Aeroz MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.