No user-submitted related servers found.
Scored across 6 tools
Each tool targets a distinct domain: passports, products, passport fields, parties, EPCIS events, and templates. Even within passports, actions like compliance and get_qr are clearly separated from basic CRUD, and _by_serial variants are explicitly scoped to avoid ambiguity.
All tools follow the consistent pattern tracepass_<resource> with snake_case, and actions use predictable verb prefixes (list, get, create, update, archive, etc.). The naming is uniform and easily navigable.
Six tools is within the ideal 3-15 range, and each tool addresses a clear functional area of DPP management. The count feels neither bloated nor sparse for the server's purpose.
The surface covers the core DPP workflow: product CRUD, passport lifecycle (create/read/suspend/archive), field updates, party management, EPCIS capture/query/export, and regulatory schema reference. Minor gaps exist, such as no explicit reactivation from suspension and immutable passport-level metadata, but these are likely intentional design constraints.
