About Aeroz
Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.aeroz.io/mcpclaude mcp add --transport http io-aeroz-aeroz https://api.aeroz.io/mcp{"mcpServers":{"io-aeroz-aeroz":{"type":"http","url":"https://api.aeroz.io/mcp"}}}Open in Cursor{"servers":{"io-aeroz-aeroz":{"type":"http","url":"https://api.aeroz.io/mcp"}}}Open in VS Code{"mcpServers":{"io-aeroz-aeroz":{"type":"http","url":"https://api.aeroz.io/mcp"}}}{"mcpServers":{"io-aeroz-aeroz":{"serverUrl":"https://api.aeroz.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://api.aeroz.io/mcpAuth requiredTools
30| Parameter | Type | Required | Description |
|---|---|---|---|
| uid | string | No | The chip UID read from the NFC tag or QR payload. Optional when SUN parameters or a tap_url carry it. |
| cmac | string | No | SUN: the `cmac` (or `c`) parameter from the same tap URL. |
| tap_url | string | No | Alternatively, the full https tap URL the phone opened (on an Aeroz host). uid, t, picc_data/e and cmac/c are read from it. |
| picc_data | string | No | SUN: the encrypted `picc_data` (or `e`) parameter from an NTAG 424 tap URL. Send with `cmac`. |
| signature | string | No | The static signature from the tag payload (the `t` parameter). Proves identity, not presence. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.