Hosted MCP server · #63 most used on Smithery
tracepass-mcp-server
malinoto/tracepass-mcp-server
MCP server for TracePass — the EU Digital Product Passport (DPP) compliance platform for the ESPR and EU Battery Regulation. Lets AI assistants create products, build and audit Digital Product Passports (battery: 91 fields; electronics: 166), set economic-operator parties, and read or capture GS1 EPCIS 2.0 supply-chain events. 6 tools, 2 resources, 5 prompts. Connect to the hosted endpoint (https://ai.tracepass.eu/mcp) with a TracePass tp_ API key, or run locally via npx -y tracepass-mcp-server.
- Uses
- 7.8k
- Tools
- 6
- Runs
- Hosted
- Prompts
- 5
- Listed
- 5mo ago
Get started
Add it to your agent
npx -y @smithery/cli@latest install malinoto/tracepass-mcp-server --client claudeSwap --client claude for cursor, vscode, windsurf or another client. The CLI asks for any required settings.
claude mcp add --transport http tracepass https://server.smithery.ai/malinoto/tracepass-mcp-server/mcpA hosted server: nothing to install. Run /mcp in Claude Code to sign in if it asks.
[mcp_servers.tracepass]
url = "https://server.smithery.ai/malinoto/tracepass-mcp-server/mcp"Add to ~/.codex/config.toml.
{
"mcpServers": {
"tracepass": {
"url": "https://server.smithery.ai/malinoto/tracepass-mcp-server/mcp"
}
}
}Add to ~/.cursor/mcp.json.
{
"servers": {
"tracepass": {
"type": "http",
"url": "https://server.smithery.ai/malinoto/tracepass-mcp-server/mcp"
}
}
}Add to .vscode/mcp.json.
gemini mcp add --transport http tracepass https://server.smithery.ai/malinoto/tracepass-mcp-server/mcpSaved to .gemini/settings.json.
What it can do
6 tools
tracepass_products2 paramsManage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit).…
Manage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit). Products are not billable on their own. Actions (pass via `action`, with `args`): - list — args: { page?, limit? (≤100), category?, status?, search? }. Read-only. - get — args: { id }. Read-only. - create — args: { name, model, category, description? }. `category` is one of: battery, textile, electronics, construction, steel, chemicals, packaging, furniture, t
| Parameter | Type | Description |
|---|---|---|
args | object | Arguments for the chosen action; required fields depend on `action` (see each action above). |
action | string | Which product operation to run: list | get | create | update. |
tracepass_passports2 paramsManage Digital Product Passports — create, read, and run lifecycle actions. IMPORTANT: `create` consumes a DPP slot on the account's plan…
Manage Digital Product Passports — create, read, and run lifecycle actions. IMPORTANT: `create` consumes a DPP slot on the account's plan and IS BILLABLE. Creating a passport beyond the included quota incurs a per-passport overage charge; if over quota the tool returns a 402-style message — only re-run with args.confirmOverage=true after the user explicitly agrees to the charge. `archive` is IRREVERSIBLE (the public QR permanently 404s); prefer `suspend` when a change might be undone. Actions (p
| Parameter | Type | Description |
|---|---|---|
args | object | Arguments for the chosen action; required fields depend on `action` (see each action above). |
action | string | Which passport operation to run. Reads: list | get | get_by_serial | compliance | get_qr. Lifecycle: create (BILLABLE) | suspend (reversible) | archive (IRREVERSIBLE), each with a _by_serial variant. |
tracepass_passport_fields2 paramsUpdate field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update. A…
Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update. Actions (pass via `action`, with `args`): - update — args: { id, fieldKey, value }. `value` type matches the field's dataType (string, number, boolean, array, object). - update_by_serial — args: { serial, fieldKey, value, gtin? }. Same as update, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call ret
| Parameter | Type | Description |
|---|---|---|
args | object | Arguments for the chosen action; required fields depend on `action`. |
action | string | Update one passport field, addressed by passport id (update) or by your serial (update_by_serial). |
tracepass_passport_parties2 paramsManage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerRes…
Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and ideally a validated 13-digit GS1 GLN. Actions (pass via `action`, with `args`): - set — args: { id, role, legalName, gln?, country?, legacyOperatorId? }. Sets or updates one role. - remove — args: { id, role }. Clears one role.
| Parameter | Type | Description |
|---|---|---|
args | object | Arguments for the chosen action; required fields depend on `action`. |
action | string | Set (add/replace) or remove an economic-operator party on a passport by its role. |
tracepass_epcis2 paramsGS1 EPCIS 2.0 supply-chain events. `export` is included on Starter plans and up; `capture`, `capture_job`, and `query` require the paid E…
GS1 EPCIS 2.0 supply-chain events. `export` is included on Starter plans and up; `capture`, `capture_job`, and `query` require the paid EPCIS add-on (those actions return a 403-style message without it). Actions (pass via `action`, with `args`): - export — args: { id }. Export a passport's events as an EPCIS 2.0 JSON-LD document. Read-only. - export_by_serial — args: { serial, gtin? }. Same as export, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in you
| Parameter | Type | Description |
|---|---|---|
args | object | Arguments for the chosen action; required fields depend on `action`. |
action | string | EPCIS 2.0: export a passport's events (export | export_by_serial), capture new events, poll a capture job, or query events. |
tracepass_templates2 paramsDiscover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the governing EU regulation. Rea…
Discover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the governing EU regulation. Read-only reference data. Use this to advise on requirements before creating products/passports, and to gap-check a draft against the rules. Actions (pass via `action`, with `args`): - list — args: {}. Lists all 12 categories with their field count, required-field count, and governing regulation (name + number + effective/mandatory dates). - get — args: { category
| Parameter | Type | Description |
|---|---|---|
args | object | Arguments for the chosen action; `category` is required for get, ignored for list. |
action | string | List all DPP category templates, or get one template by category. |
Ready-made
Prompts
audit_passportReview one Digital Product Passport for completeness and compliance readiness — which required fields are missing, which economic-operator parties are unset, whether it's publishable.onboard_productWalk through creating a new product and its first Digital Product Passport — gathering the details, then creating both.explain_dpp_requirementsExplain what a Digital Product Passport in a given category must contain to be compliant — the required fields and the EU regulation behind them — before you create anything.compliance_gap_checkCross-check a draft passport against its category's regulatory schema and produce an exact, prioritised list of what's missing before it can be published compliantly.review_epcis_eventsInspect the EPCIS 2.0 supply-chain event history of a passport and summarise the product's traceability story.
Readable data
Resources
productsThe account's TracePass product catalogue (first page). Attach this for an overview of what products exist.templatesAll 12 DPP category schemas with field count, required-field count, and governing regulation. Attach this to ground the model in what each category's compliance requirements are.