No user-submitted related servers found.
Scored across 7 tools
The seven top-level tools map to clearly distinct domains: product catalogue, passport lifecycle, passport fields, economic-operator parties, EPCIS events, template schemas, and legal scope. Boundary risk is mostly inside tracepass_passports, whose many paired *_by_serial actions overlap conceptually with their by-id siblings, though the descriptions explicitly disambiguate (serial uniqueness, 409 ambiguous_serial, GTIN disambiguation).
All tools share the tracepass_ prefix and a consistent resource-noun layout, with actions expressed uniformly as verbs via the action parameter. Minor deviations: plural 'products'/'passports' vs singular 'passport_fields'/'passport_parties', and parties uses set/remove while fields uses update, but the pattern is still highly predictable.
Seven top-level tools is well within the ideal 3-15 range for a DPP platform and each tool earns its place. However tracepass_passports concentrates roughly 25 actions (list/get/QR/snapshots/condition flags/measurements/compliance/registry/place_on_market plus many *_by_serial variants), making that one tool disproportionately heavy.
The surface covers products, passport create/read/lifecycle, field updates, parties, EPCIS capture/query/export, templates, and scope checking, which is broad lifecycle coverage. Gaps remain: publishing is explicitly out of band (dashboard only), products have archive but no unarchive, and parties offer set/remove but no dedicated read action.
