Tracepass MCP Server

What malinoto/tracepass-mcp-server MCP server does

malinoto/tracepass-mcp-server exposes TracePass capabilities to MCP-compatible AI clients. It works with the product catalogue and the serialized Digital Product Passports associated with those products. Products can be listed, created individually or in batches, updated, and soft-archived. Passports can be read by TracePass ID or by a customer serial number, created, suspended, archived, and served as SVG or PNG QR codes.

The server covers 13 product categories, including batteries, textiles, electronics, construction, steel, packaging, furniture, tyres, toys, and fast-moving consumer goods. Template queries provide category field definitions, data types, access levels, validation rules, requiredness, and related EU regulatory references. Passport operations also include compliance checks, battery registry-readiness checks, field updates, and economic-operator party management.

How it works

malinoto/tracepass-mcp-server groups API operations into six MCP tools. Each tool receives an action and an action-specific argument object. The hosted endpoint is https://ai.tracepass.eu/mcp; the local package runs with npx -y tracepass-mcp-server and communicates over stdio.

Serial-based actions use the caller's serial number, but serials are unique only within a GTIN. If a serial is ambiguous, supply the GTIN or use the passport ID. Passport field changes are recorded in the audit trail and identified as API-key updates.

The compliance result is a three-level verdict with regulation-cited findings. Registry readiness is a separate mechanical check for battery passports and does not establish substantive compliance. Battery measurement actions can record changing operational data over the passport's lifetime, where supported by the account plan.

Setup and configuration

For local use, provide a TracePass API key to the subprocess:

{
  "mcpServers": {
    "tracepass": {
      "command": "npx",
      "args": ["-y", "tracepass-mcp-server"],
      "env": { "TRACEPASS_API_KEY": "tp_YOUR_KEY" }
    }
  }
}

Hosted clients can point to https://ai.tracepass.eu/mcp and send the key as a Bearer token. Hosted access also supports OAuth 2.0 with authorization-code flow and PKCE; local stdio use is API-key only. TRACEPASS_BASE_URL can override the default API deployment URL, which is https://app.tracepass.eu.

Tools and capabilities

• tracepass_products: catalogue listing, lookup, creation, batch creation, updates, and soft archival.
• tracepass_passports: passport listing, lookup, creation, compliance and registry checks, suspension, archival, QR retrieval, snapshots, condition flags, and battery measurements.
• tracepass_passport_fields: update category-specific values by ID or serial.
• tracepass_passport_parties: set or remove manufacturer, importer, distributor, recycler, authorised representative, and related roles.
• tracepass_epcis: export passport events, capture JSON-LD EPCIS documents, poll capture jobs, and query events.
• tracepass_templates: inspect regulatory schemas for each supported category.

Limitations and notes

malinoto/tracepass-mcp-server does not make passport creation free: each creation consumes a DPP slot, and over-quota creation requires explicit confirmOverage consent after the user agrees to the charge. Passport archival is irreversible and makes its public QR return 404; suspension is reversible. Product archival is reversible but blocked while active passports reference the product.

EPCIS export is available on Starter plans and above, while capture, capture-job polling, and query require the paid EPCIS add-on. Compliance results reflect the rules encoded by TracePass and are not legal advice or proof that a product can be placed on the market. Battery template requirements depend on whether the battery category is in scope, so the category-specific rules must be resolved before declaring fields mandatory.