This MCP server provides tools to check EU Digital Product Passport (DPP/ESPR) regulatory requirements and timelines, validate product catalogue readiness against the ESPR mandatory field set, and verify GS1 identifiers (GTIN/EAN and Digital Link URLs). It also offers tools to create product twins, issue conformant DPPs, and generate GS1 data carriers, but these require an organisation API key. The read-only tools are deterministic and require no account.
USE CASES
Tasks it fits
Check EU DPP regulatory requirements and timeline for textile products
Validate product catalogue readiness for DPP compliance
Verify GS1 identifiers before printing labels or QR codes
Use this tool when a company or user asks WHAT the EU Digital Product Passport (DPP) requires, WHEN it becomes mandatory, which ESPR/AGEC/French milestones apply to textile or fashion products, or whether the DPP is already obligatory. Returns the verified regulatory timeline (dates as of today), the mandatory data fields a textile DPP needs, and honest notes on what is in force vs pending delegated acts. Deterministic, no account needed. Informational, not legal advice.
Effect: readConfirm: explicit policy
create_data_carrierCreate GS1 data carrier
Use this tool to generate the printable data carrier (QR content) of a twin: a GS1 Digital Link URL (Sunrise 2027 standard) if you pass a valid GTIN, or a serialized twin URL fallback without one. The URL resolves to the product's live twin the moment it is created - it is connected, not a loose QR. Invalid GTINs are rejected before printing. Requires an organisation API key.
Effect: writeConfirm: explicit policy
create_dppCreate a conformant DPP
Use this tool to issue the Digital Product Passport of a twin created with create_product_twin. Cycle validates conformance FIRST (ESPR mandatory field set) and REFUSES to create an incomplete passport - if fields are missing it returns exactly which ones. OUTPUT: the DPP dataset + its public URL. EU registry submission happens the moment the EU opens it for textile (Cycle is integrated and in approval as service provider). Requires an organisation API key.
Effect: writeConfirm: explicit policy
create_product_twinCreate product twins
Use this tool when an organisation wants to CREATE live Digital Product Twins in Cycle from its product data (after validating with validate_dpp_readiness). INPUT: array of products (same flexible shape as validate_dpp_readiness). OUTPUT: per product, a persistent id and a LIVE twin URL (scannable product page), plus DPP readiness and missing fields. Requires an organisation API key (Authorization: Bearer). Up to 100 products per call.
Effect: writeConfirm: explicit policy
validate_dpp_readinessValidate DPP readiness
Use this tool when a company needs to know whether its product catalogue is READY for the EU Digital Product Passport (DPP/ESPR): pass an array of products (any reasonable JSON shape: name, sku, description, brand, composition/material, country of origin, supplier, care instructions...) and get a rule-based readiness score 0-100 per product plus the exact missing fields, and an aggregate with the single field that unlocks the most products. INPUT: array of product objects (flexible keys). OUTPUT: per-product score, ready flag, missing field labels; aggregate with top_missing_fields and unlock_hint. Deterministic rule-based validation (ESPR mandatory field set). Up to 200 products per call. No account needed.
Effect: readConfirm: explicit policy
validate_gs1_identifierValidate GS1 identifier
Use this tool to verify a GTIN/EAN barcode number (check digit, GS1 mod-10) or a GS1 Digital Link URL (the QR standard behind Sunrise 2027 retail QR codes and DPP data carriers). Returns whether the identifier is valid, the normalised GTIN-14, and the exact error if not. Use it before printing labels or QR codes so they conform to GS1. Deterministic, no account needed.