tracepass-mcp-server
A Model Context Protocol server for TracePass, the EU Digital Product Passport platform, letting AI assistants manage products, passports, economic-operator parties, GS1 EPCIS 2.0 supply-chain events, DPP scope checks and access grants.
Products (
tracepass_products): list, get, create (single or batch up to 100), update, list a product's published passport links, and render its model-page QR.Passports (
tracepass_passports): list, get by id or serial, run compliance and EU DPP Registry readiness checks, prepare Registry UPI/upload files, record acceptance tests, read/set condition flags, create drafts (incl. battery second-life lineage), get QR codes, and read snapshot history.Passport fields (
tracepass_passport_fields): update category-specific field values by id or serial, marked manual orai_suggestedfor human review.Parties (
tracepass_passport_parties): set or remove economic-operator roles (manufacturer, importer, recycler, etc.) with legal identifiers.EPCIS 2.0 (
tracepass_epcis): export, capture, poll capture jobs, and query GS1 supply-chain events.Templates (
tracepass_templates): read the 13 DPP category field schemas, each field traced to its mandating EU instrument.Scope checker (
tracepass_scope): check whether a product type needs a passport, read the catalogue-wide scope report, and trigger/poll catalogue refresh runs.Lifecycle (
tracepass_passport_lifecycle): record/undo Registry registration, place on market, suspend, archive passports, and archive products — irreversible or legal acts requiring confirmation.Access grants (
tracepass_access_grants): create, update, revoke and audit partner grants for restricted data (secret token shown once).Resources & prompts: read-only context URIs (products, passports, EPCIS, compliance, snapshots, templates, reference docs) plus slash-command workflows like
audit_passport,onboard_productandregister_battery_passport.Extra endpoints: supplier data-request tools and a DPP-law assistant at
/compliance/mcp; auth via API key or OAuth 2.0.
Supports ISO 26324 DOI identifiers for Digital Product Passports: passports can be created with a DOI identifier (bare 10./, with required model/batch/item granularity), any https://doi.org/ or doi: prefix is stripped on input, and the identifier resolves as https://doi.org/. DOI identifiers are rejected for battery passports, which accept only GS1 and ISO/IEC 15459.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
TracePass MCP Server
A Model Context Protocol server for TracePass — the EU Digital Product Passport platform. It lets AI assistants (Claude, Cursor, IDE agents) manage products, Digital Product Passports, economic-operator parties, and GS1 EPCIS 2.0 supply-chain events.
It speaks the full MCP protocol — tools, resources, resource templates, and prompts.
Two ways to use it
The same server core ships two ways:
Hosted — point your MCP client at
https://ai.tracepass.eu/mcp. Nothing to install; always current.Local (npm) — run
tracepass-mcp-servervianpx. The MCP client launches it as a subprocess and speaks MCP over stdio.
Related MCP server: fallpharm-mcp
Authentication
The server accepts either of TracePass's two v1 auth methods on the
same Authorization: Bearer … header — it forwards whatever you send to
the API, which decides. Pick the one that fits how you're connecting:
API key | OAuth 2.0 | |
Best for | A single user, scripts, server-to-server | AI assistants / apps acting on a user's behalf |
What you send | A static | A scoped access token obtained via the OAuth flow |
Setup | Mint at Developer → API Keys | The user clicks Connect and approves scopes |
Scope | All-or-nothing (the whole workspace) | Exactly the scopes the user granted; revocable |
Works with | Hosted and local (npx) | Hosted endpoint only (needs a browser consent step) |
Which should an AI assistant use? If your MCP client supports OAuth (Claude.ai, ChatGPT, and others), prefer OAuth — the user authorizes the connection once on a TracePass consent screen, you never handle a secret, and access is least-privilege and revocable. If your client only takes a header/token, use an API key.
OAuth 2.0 (recommended for hosted clients)
No config beyond pointing your client at the hosted endpoint — discovery
is automatic. On the first unauthenticated request the server returns a
401 whose WWW-Authenticate header carries a resource_metadata URL
(RFC 9728) pointing at /.well-known/oauth-protected-resource, which
names the TracePass authorization server. The client runs the standard
authorization-code flow with PKCE (/api/oauth/authorize →
/api/oauth/token), the user approves scopes, and the client stores +
refreshes the token. If you distribute your own client, register an app
under Developer → OAuth Apps to get a client_id; many hosted
clients self-register via Dynamic Client Registration automatically.
Request only the scopes you need, e.g. passports:read passports:write offline_access; managing access grants needs access_grants:read / access_grants:write. Users manage connected apps (and revoke) under
Developer → OAuth Apps → Connected Apps.
API key
Mint a tp_… key under Developer → API Keys and send it as a Bearer
token.
Hosted:
{
"mcpServers": {
"tracepass": {
"url": "https://ai.tracepass.eu/mcp",
"headers": { "Authorization": "Bearer tp_YOUR_KEY" }
}
}
}Local (npx / stdio) — the local subprocess can't do an interactive
OAuth consent step, so it's API-key only, via the TRACEPASS_API_KEY env:
{
"mcpServers": {
"tracepass": {
"command": "npx",
"args": ["-y", "tracepass-mcp-server"],
"env": {
"TRACEPASS_API_KEY": "tp_YOUR_KEY"
}
}
}
}Optional env vars:
Var | Default | Purpose |
|
| Override the TracePass API base URL (e.g. point at a local stack). |
|
| Public OAuth authorization-server origin advertised in discovery metadata. Set this when |
|
| Maximum request body size. Requests over the limit are rejected with 413 before reaching the SDK. |
|
| Maximum JSON-RPC messages in a single batch request. Oversized batches are rejected with 400 |
|
| Listen port for the hosted HTTP service. |
The hosted endpoint accepts POST only on /mcp, /compliance/mcp, and the supplier paths. GET and DELETE are rejected with 405 to prevent the SDK's stateless transport from opening an unbounded SSE stream.
Tools
The TracePass v1 API operations are grouped into 9 tools. Each takes an action enum plus action-specific arguments. The tools are:
tracepass_products- manage the product catalogue (list, get, create, create_batch, update products; get_links lists every published passport link of a product plus its model page, get_model_qr renders the model page QR).tracepass_passports- manage Digital Product Passports (list, get, compliance check, registry-readiness check, prepare an EU DPP Registry registration, record an acceptance test, get/set condition flags, create, get QR, list snapshots, get snapshot), by id or by serial. Passports are identified via GS1 or four additional EN 18219 schemes (iso15459, iec61406, did, doi); battery passports accept only gs1 and iso15459 (Art. 77(3)). Condition flags are approved yes/no facts (e.g. battery:hasBMS,rechargeable,externalStorageOnly,isStationaryBess) that gate conditional legal duties — setting an approved flag may make additional fields required and block publishing if those fields are empty.tracepass_passport_fields- update a passport's category-specific data fields, by id or by serial.tracepass_passport_parties- set or remove a passport's economic-operator parties (manufacturer, importer, etc.).tracepass_epcis- export, capture, and query a passport's GS1 EPCIS 2.0 supply-chain events.tracepass_templates- list and get the DPP category field schemas, each field traced to the EU instrument that mandates it.tracepass_access_grants- share restricted passport data with a partner through an access grant and manage the grants issued (list, get, create, update, revoke, activity). The secret token is returned once on create. Needs an OAuth connection approved for theaccess_grants:read/access_grants:writescopes, or an API key with "May manage access grants" switched on in the dashboard; authority-role grants are dashboard-only end to end (create, update and revoke are refused through the API).tracepass_scope- check whether a product type needs a Digital Product Passport (check), read the company's catalogue-wide scope report (catalogue_report), and trigger or poll a catalogue refresh run (catalogue_run, catalogue_run_status).tracepass_passport_lifecycle- irreversible and public-facing passport and product lifecycle actions (record_registration, undo_registration, place_on_market, suspend, archive, archive_product); the assistant must confirm with the user before each call.
Each tool's full action set:
Tool | Actions |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Restricted and authority passport data is read through access grants the owner issues in the TracePass dashboard (role, scope, purpose, expiry); tracepass_access_grants lists, creates, changes and revokes them for the non-authority roles (authority grants are dashboard-only). A GTIN-only address (no serial) answers a public model page of the product, not a unit's passport.
Changed in 1.24.0: archive, archive_by_serial, suspend, suspend_by_serial, and place_on_market moved from tracepass_passports to tracepass_passport_lifecycle; archive on products moved there as archive_product. This separates irreversible and public-facing actions so a client's "always allow" on the read-only passport tool no longer also allows them. Calls to the old names on the old tools return an error naming the new tool.
The *_by_serial actions address a passport by the customer's own serial
number instead of its TracePass id. A serial is unique only within a GTIN, so
if the same serial exists under two GTINs in your account a serial-only call
returns 409 ambiguous_serial — pass the optional gtin arg to disambiguate
(or use the by-id action). The same gtin disambiguator applies to every
*_by_serial action.
The tracepass_passports compliance action returns a three-tier
compliance verdict (compliant / compliant_with_warnings /
incomplete) with regulation-cited findings — missing required fields,
missing economic-operator parties, format issues, and per-category
conditional rules. Read-only; use it to gap-check a passport, fix the
cited gaps, then re-check.
A compliant verdict means this passport satisfies the rules encoded here,
not this product may be placed on the market. The field specifications are
hand-authored from the regulations, not an official EU artefact, and delegated
acts are still landing. It is not legal advice.
Second-life batteries
A repurposed, remanufactured or reused battery needs a new passport
linked to the original one(s) (Battery Regulation Art. 77(7)). Pass a
lineage block to tracepass_passports create:
{
"predecessors": [
{ "internalPassportId": "<your original passport id>", "trigger": "repurposing" }
]
}A predecessor is named by internalPassportId (one of your own passports)
or by its resolvable identifier. trigger is one of
preparation_for_reuse, preparation_for_repurposing, repurposing or
remanufacturing. The platform derives batteryStatus from the
triggers, stores the block immutably, and links your own originals back
to the new passport (successors). A battery placed on the market before
18 Feb 2027 has no original passport: send an empty list with
noPredecessorReason. Rule violations return 422 with the rule code.
Battery measurements (living record)
capture_measurements pushes over-life data from your own equipment into a
published battery passport: state of health, fades, cycle counts, dynamic
values, state of charge, negative events, temperature history (Battery
Regulation Annex XIII point 4). Every measurement is kept; the newest per
field becomes the passport's current value and sets dynamicDataAsOf.
list_measurements and latest_measurements read them back.
They are metered against the plan's monthly measurement allowance, not the daily write budget. Paid plans keep counting past the allowance at no charge; the Free plan stops at its allowance. Reading a passport is never metered.
Registering a battery passport in the EU DPP Registry
The economic operator registers a battery passport itself, on the EU DPP Registry website under its own EU Login. TracePass prepares what the operator submits and records what the operator reports; it never submits to the Registry and never verifies the outcome.
tracepass_passportsregistry_readiness— would the Registry's formal checks pass?tracepass_passportsprepare_registry_upireturns the exact address (upi) to paste into the Registry's online form. For several passports,prepare_registry_upload_file({ passportIds }, up to 100) returnsxmlto upload unchanged underfilename; passports that would fail are left out and listed inexcludedwith a reason, because the Registry fails a whole file on one bad entry.The Registry's acceptance environment is for testing and has no legal effect:
tracepass_passportsrecord_acceptance_testrecords its result and changes nothing else.After registering in production,
tracepass_passport_lifecyclerecord_registrationrecords it (placedOnMarketAtdefaults to today): the passport is marked placed on the market and its operator and facility identifiers lock.undo_registrationremoves a mistaken record.
These actions need a paid plan; a connected app (OAuth) must act for an
admin or owner. place_on_market submits to an EN 18222 registry API and is
not a way into the EU DPP Registry, which does not accept it.
A note on writes
Some actions cost money or are irreversible — the server's tool descriptions tell the model so:
tracepass_passportscreatemakes a draft passport. A draft takes no plan DPP slot and is not billed; the slot, and any overage past the plan cap, is taken when the passport is published in the TracePass dashboard. Each create counts against the daily write budget.tracepass_passport_lifecyclearchiveis irreversible — it takes the passport off public view (its URL shows an archive notice, machine formats answer 404, and only an authority access grant still reads it). Usesuspend(reversible) when a change might be undone.record_registrationrecords the operator's registration in the production EU DPP Registry and locks the passport's operator identifiers.place_on_marketis a legal act (a registration through an EN 18222 registry API). These actions live on a separate tool so an "always allow" on reading does not also allow them.tracepass_epcis—export,captureandqueryare on every plan, Free included; captured events count against the plan's event allowance, andcaptureover it returns an overage or hard-block message.
Resources
Read-only entity data you can attach as conversation context:
tracepass://products— the product cataloguetracepass://product/{id}— one producttracepass://passport/{id}— one passport, full field detailtracepass://passport/{id}/epcis— a passport's EPCIS 2.0 eventstracepass://passport/{id}/compliance— a passport's compliance verdicttracepass://passport/{id}/registry-readiness— a mechanical pre-submission check modelled on the EU DPP Registry's formal gate: mandatory-field presence, formatting, a resolvable public link, item-level granularity, and a well-formed commodity code only where the category carries one (none for batteries: a battery passport's registration identifier is not entered in the customs declaration), and, for EV, LMT and industrial (over 2 kWh) batteries, conformance to the Commission's published battery data model that the Registry validates against. Not the substantive compliance verdict, and not a guarantee of the real registry's response: the Registry does not yet run its battery semantic validation. Battery only.tracepass://passport/{id}/snapshots— the snapshot history of a passport (newest first): a snapshot on publish and after every change to a non-draft passport; each entry carries version, reason (e.g. published, field_edit, status_change, baseline), actor, snapshotAt, contentHash, hashMethod (jcs-sha256for new snapshots,sorted-json-sha256for older ones), previousHash (hash chain), hashValid (re-verified on read), chainLink, and a list-level chain verdict, restorable flag, and field count.tracepass://templates— all 13 DPP category field schemastracepass://template/{category}— one category's full field schematracepass://reference/{passports|lifecycle|scope|parties|templates}— long-form reference the tool descriptions point at (identifier scheme shapes, refusal codes, EU DPP Registry action detail, scope argument values). Kept out of the tool descriptions sotools/liststays small; read on demand
Prompts
Reusable DPP workflows the client surfaces as slash-commands:
audit_passport— review a passport for completeness and compliance readinessonboard_product— create a product and its first passportexplain_dpp_requirements— explain what a category's compliant DPP must contain, and the regulation behind each fieldcompliance_gap_check— produce a prioritised, regulation-cited list of what's blocking a passport's compliant publicationregister_battery_passport— walk the operator through registering a published battery passport in the EU DPP Registry: readiness, the address or upload file to submit on the Registry website, then recording the resultreview_epcis_events— summarise a passport's supply-chain trail
For suppliers: answering a data request
A second, separate endpoint serves suppliers who receive a TracePass data request. It is not part of the tools above. The request email carries a personal address:
https://ai.tracepass.eu/supplier/mcp/<token>Add it to an AI assistant as a custom connector. For clients that can set
headers, https://ai.tracepass.eu/supplier/mcp with
Authorization: Bearer <token> works too. The token authorises that one
request only; there is no account and no OAuth. The assistant can then:
Tool | What it does |
| Start here: who is asking, for which product, and every field asked for, each with its meaning, unit, format and legal source; plus answers already sent and the review outcome |
| A dry run: what would be stored, which keys were not requested, and what does not fit. Writes nothing |
| The best way to attach a datasheet or certificate when the assistant can run shell commands: returns a |
| Attach a very small file (a few kilobytes) inline as base64; prefer |
| Send answers with evidence per value to the requester's human review; can be repeated (answers merge) until reviewed |
| Whether the requester has reviewed them, the outcome, accepted fields, and when the link expires |
Answers go to the requester's human review; they never publish anything on their own.
DPP Assistant: EU passport questions
A third endpoint answers questions about EU Digital Product Passport law for anyone with a free TracePass account:
https://ai.tracepass.eu/compliance/mcpAdd it to an AI assistant as a custom connector (in Claude: Customize → Connectors → "+ Add" → "Add custom connector"), then sign in with a TracePass account when asked. It uses OAuth; no API key is needed. Answers cite their source, and each company gets about 100 answers a day. Full guide: tracepass.eu/docs/dpp-assistant.
Tool | What it does |
| Whether EU law requires a passport for a type of product, from when, and what it requires of each role |
| The data a passport must contain for a category, with the article requiring each field and who may see it |
| Changes in EU passport law and standards for your categories since a date; planned items are marked as not yet law |
| The EU DPP Registry and the technical side: registration, identifiers, data carriers, formats and standards |
| Creates a draft passport in your own account; publishing stays with you in TracePass |
| Reports an answer you think is wrong or unclear, for review |
| The company facts the assistant remembers between questions, so you do not repeat them |
Development
npm install
npm run build # tsc -> dist/
npm run typecheck
npm test # vitest
npm run lint
npm start # run the hosted HTTP service locally (:8080)
npm run start:stdio # run the stdio server locallyThe hosted service is a plain Node HTTP server (dist/http.js),
stateless — each request carries its own API key and builds a fresh
MCP session. It is containerised via the Dockerfile; the hosted endpoint
runs in the EU.
Listed on Glama
This server is published in the official MCP Registry
as eu.tracepass/tracepass and listed on Glama:
License
MIT
Available Tools
9 toolstracepass_access_grantsTracePass access grantsADestructiveInspect
Share restricted passport data with a partner (repairer, recycler, purchaser...) through an access grant, and see or end the grants already issued. A grant names a role, a scope (company, chosen products or chosen passports), a purpose, optional evidence and an expiry (default 12 months). Needs an OAuth connection approved for access grants or an API key with "May manage access grants" switched on (403 access_grants_not_enabled); writing needs an admin. Authority roles (e.g. market surveillance) are dashboard-only end to end: create, update and revoke of such a grant are refused (400 role_dashboard_only).
IMPORTANT: create returns the secret pa_ token ONCE. Hand it to the recipient and do not repeat it, store it or put it in a log. It cannot be shown again; if lost, revoke the grant and create a new one. A confirmed grant gives a third party access to restricted data: confirm the recipient, role, scope and purpose with the user first.
Actions (pass via action; {…} is the args object). Reads never return a token.
list — { limit? (≤100), cursor?, role?, status? (active|expired|revoked), passportId?, productId? }.
get — { id }.
create — { role, label, purpose?, scope? ({ kind: company } with no ids, or { kind: products|passports, ids[] } with at least one id), evidence? ({ type: register_entry|invoice|authority_letter|contract|other, reference, note? }), expiresInDays? (1-1825; null = no expiry) }. WRITE.
update — { id, label?, purpose?, scope?, evidence?, expiresInDays? }; at least one. WRITE.
revoke — { id }. WRITE, ends the grant at once; repeating it is safe.
activity — { id, limit? (≤100), cursor? }. The grant's access log.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_epcisTracePass EPCIS 2.0AInspect
GS1 EPCIS 2.0 supply-chain events. export, capture, capture_job and query are on every plan, Free included. Captured events count against the plan's event allowance (10 a month on Free); over it capture returns an overage or hard-block message.
Actions (pass via action; {…} is the args object):
export, export_by_serial — { id } or { serial, gtin? } (on 409 ambiguous_serial pass
gtin). A passport's events as an EPCIS 2.0 JSON-LD document. Read-only.capture — { events }. An EPCISDocument, a single event, or an array of events (JSON-LD). Returns 202 with a captureJobId.
capture_job — { jobId }. Poll a capture job. Read-only.
query — { params? }. Standard EPCIS query parameters as key/value (EQ_bizStep, GE_eventTime, MATCH_epc, …). Read-only.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_passport_fieldsTracePass passport fieldsADestructiveIdempotentInspect
Update field values on a Digital Product Passport. Every change is audit-logged with the credential (API key or connected app) and this MCP channel.
source (optional): omit it or pass "manual" when the user gave you the value or it comes from their own records — written with the user's rights (approved for an API key or an admin; sent to review for a connected app acting for an editor). Pass "ai_suggested" when you found or inferred it yourself: it goes to the dashboard review queue for a human, and is refused on fields only the operator may state or that must be measured (e.g. stateOfHealth).
Actions (pass via action; {…} is the args object):
update — { id, fieldKey, value, source? }.
valuetype matches the field's dataType.update_by_serial — { serial, fieldKey, value, gtin?, source? }. On 409 ambiguous_serial (a serial is unique only WITHIN a GTIN) pass
gtin.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_passport_lifecycleTracePass passport lifecycle (irreversible actions)ADestructiveInspect
WARNING: Every action here changes what the public sees or is a legal act, some irreversible. archive permanently takes the passport off public view (its URL shows an archive notice; only an authority access grant still reads it). record_registration records the economic operator's registration in the production EU DPP Registry and locks the passport's operator and facility identifiers. place_on_market submits a registration to an EN 18222 registry API. The assistant MUST confirm with the user before each call. Use suspend (reversible — public QR shows 'suspended') as the safe alternative to archive when a change might need to be undone; a passport placed on the market cannot be suspended, because it must stay public.
EU DPP REGISTRY: the operator registers a battery passport itself, on the Registry website under its own EU Login; TracePass never submits to the Registry and never verifies the outcome. The acceptance environment has no legal effect; only a production registration counts. Paid plan; a connected app (OAuth) must act for an admin or owner. Refusal codes: resource tracepass://reference/lifecycle.
Actions (pass via action; {…} is the args object). All are WRITEs (1 write each). A *_by_serial action takes { serial, gtin? } instead of id (on 409 ambiguous_serial pass gtin).
record_registration — { id, placedOnMarketAt? (YYYY-MM-DD), registrationId? }. Battery, published only. Records that the operator has registered this passport in the PRODUCTION EU DPP Registry, as the operator states it; TracePass does not check it. Confirm with the user first, and only after the operator has registered on the Registry website. Effects: marked placed on the market; operator and facility identifiers locked (409 operator_locked); webhook fires.
undo_registration — { id, environment: production|acceptance }. Undoes a mistaken record; production unlocks the operator identifiers (a delivered webhook is not recalled). Changes nothing in the Registry. Confirm with the user first.
place_on_market — { id }. Battery, published only. Submits to the EN 18222 registry API in the account's registry settings. NOT the way into the EU DPP Registry, which does not accept it: use prepare_registry_upi / prepare_registry_upload_file, then record_registration. A legal act for the economic operator — confirm with the user first. ASYNCHRONOUS: answers 202 "placing"; follow placeOnMarketStatus (placing → placed | rejected) by reading the passport. 409 codes include registry_host_not_allowed (the configured registry address is not allowed; check the URL) and registry_not_ready (run registry_readiness).
suspend, suspend_by_serial — { id }. Reversible — public QR shows 'suspended'. Refused with 409 passport_placed_on_market once the passport is placed on the market or its registration is under way.
archive, archive_by_serial — { id, reason? }. IRREVERSIBLE and destructive — confirm with the user first. Its URL then shows an archive notice (machine formats 404); only an authority grant still reads it. reason is REQUIRED for battery passports (400 reason_required): recycled, never_placed (never placed on the market or put into service) or duplicate_or_error; never_placed is refused (409 reason_contradicts_placement) once placed on the market.
archive_product — { id }. Archives a PRODUCT (not a passport). Reversible — soft-archives it from the catalogue. 409 while any non-archived passport references it; archive those first.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_passport_partiesTracePass passport partiesADestructiveIdempotentInspect
Manage the economic-operator parties on a passport (manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg). Each carries a legal name and an identifier.
A party needs at least one of gln, legacyOperatorId or operatorIdentifier (EN 18219 §6.2–6.5; they must agree if both gln forms are given, else 400). Identifier shapes: resource tracepass://reference/parties.
Actions (pass via action; {…} is the args object):
set — { id, role, legalName, gln?, country?, url?, tradeName?, postalAddress?, email?, legacyOperatorId?, operatorIdentifier?, facilityIdentifier? }. tradeName, postalAddress and email are public; for a battery importer they are its Battery Regulation Art. 41(3) details.
remove — { id, role }.
After a battery passport is placed on the market, changing a stored operatorIdentifier or facilityIdentifier returns 409 operator_locked; other edits stay allowed.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_passportsTracePass passportsADestructiveInspect
Manage Digital Product Passports — create, read, run compliance checks. Archive, suspend, place on market and record_registration are in tracepass_passport_lifecycle.
IMPORTANT: create makes a DRAFT passport: no plan DPP slot, never billed. The slot, and any overage past the plan cap, is taken when it is published in the TracePass dashboard, not through this tool. Each create counts against the daily write budget.
EU DPP REGISTRY (battery): the operator registers a passport itself, on the Registry website under its own EU Login. TracePass prepares what it submits and records what it reports; it never submits to the Registry and never verifies the outcome. The acceptance environment has no legal effect; production is recorded with record_registration (tracepass_passport_lifecycle). Paid plan; an OAuth app must act for an admin or owner.
Identifier schemes (EN 18219): gs1 | iso15459 | iec61406 | did | doi; batteries accept ONLY gs1 and iso15459. Shapes, lineage, snapshots, measurements, refusal codes: resource tracepass://reference/passports.
Actions (pass via action; {…} is the args object). Read-only unless marked WRITE. A *_by_serial action takes { serial, gtin? } instead of id (on 409 ambiguous_serial pass gtin).
list — { page?, limit? (≤100), productId?, status?, search? }. status ∈ draft|in_review|approved|published|suspended|expired|archived.
get, get_by_serial — { id, format? (summary|full), lang? }.
compliance — { id }. compliant | compliant_with_warnings | incomplete, with regulation-cited findings and byRegulation[]. A regulation absent from byRegulation raised no finding, which is not the same as passed.
registry_readiness — { id }. Battery only. { ready, findings[] }: the Registry's FORMAL pre-submission check, not the compliance verdict.
prepare_registry_upi — { id }. WRITE, battery, published only. { upi, preparedAt } for the operator to paste into the Registry form. Submits nothing.
prepare_registry_upload_file — { passportIds (1–100) }. WRITE, battery. { xml, filename, included, excluded }: the operator uploads
xmlon the Registry website; TracePass does not. 1 write per included passport.record_acceptance_test — { id, result: passed|failed, errorCode? }. WRITE, battery, published only. Records what the operator reports from the ACCEPTANCE environment: no legal effect, not verified. Undo: undo_registration (acceptance).
create — { productId, identifier?, gtin?, serialNumber?, lineage? }. Draft, not billed. identifier preferred, or legacy gtin + serialNumber. Battery: only gs1/iso15459, else 400. Duplicate: 409. lineage (battery): a repurposed, remanufactured or reused battery needs a NEW passport linked to the original(s) (Art. 77(7)); immutable after create.
get_qr, get_qr_by_serial — { id, format? (svg|png), symbology? (qr|datamatrix) }. One passport's QR; the bare GTIN URL is the product's model page (see products get_links).
list_snapshots — { id, page?, limit?, at? (ISO 8601) }; get_snapshot — { id, snapshotId }. EN 18221 change archive (
at= the snapshot valid then). Entries carry contentHash, hashMethod (jcs-sha256 = RFC 8785 + SHA-256; older: sorted-json-sha256), previousHash and, in the list, chainLink plus a chain verdict. 1 read each.get_condition_flags, _by_serial — { id }. Approved yes/no facts that gate conditional duties; an approved flag can make fields required and block publish. 1 read.
set_condition_flags, _by_serial — { id, flags: Record<flagKey, boolean|null> }. WRITE; null clears. WARNING: approving a flag can make fields required and block publishing if empty — fix them before or right after.
capture_measurements, _by_serial — { id, measurements: [ { fieldKey, value, measuredAt (ISO 8601), externalId?, unit? } ] (≤500) }. WRITE, battery, published only. Over-life data from the customer's equipment; metered against the monthly measurement allowance, not the write budget.
list_measurements, _by_serial — { id, fieldKey?, from?, to?, limit? (≤200), cursor? }; latest_measurements, _by_serial — { id }. Read-only.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_productsTracePass productsADestructiveInspect
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. Archive is in tracepass_passport_lifecycle.
Actions (pass via action; {…} is the args object):
list — { page?, limit? (≤100), category?, status?, search? }. Read-only.
get — { id }. Read-only.
create — { name, model, category, description? }.
categoryis one of the 13 DPP categories (tracepass_templates list).update — { id, name?, model?, description? }; at least one field.
get_links — { id, format? (json|csv), limit? (≤5000), cursor? (json: prior nextCursor) }. Every PUBLISHED passport's serial, passportUrl, status (json adds qrApiUrl, needs your API credentials) plus the model page URL, for a dealer asking for passport links.
get_model_qr — { id, format? (svg|png), gtin? (14 digits) }. QR of the model page. 404 model_not_found; 400 gtin_required (several GTINs) or invalid_gtin.
create_batch — { products: [ { name, model, category, description? }, … ] }, up to 100. Partial-success: per-item status, so some can be created while others error. The batch consumes N writes upfront; if that would exceed the daily cap NOTHING is created (429).
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_scopeTracePass DPP scope checkerAInspect
Check what EU law says for a product type matching the facts given: whether it needs a Digital Product Passport, from when, at which level, under which act and article, and the duties of each role. Also reads the catalogue-wide scope report and triggers a refresh run.
HARD RULES — always apply to scope answers:
State what the law says for product types matching the given facts. Not legal advice; never write 'you must' — use product-type phrasing ('LMT batteries need a passport from 18 February 2027, Battery Regulation Art. 77(1)').
Cite the article given for every verdict and duty; a regulation without an article is not a citation.
not_coveredrests on no article: say our rules do not cover the product, name the nearest act given, never cite it as the basis.A date with precision 'quarter', 'month' or 'year' is a plan, NEVER a deadline: write 'planned for Q2 2027 (planned, not law yet)', never 'from', 'by' or 'deadline'.
Relay
not_coveredandneeds_inputas results, never errors.needs_input= blocking questions remain — relayask[]to the user before giving a verdict.Items in an act's
plannedlist are not law yet: label them 'Planned, not law yet' (labelText), with theirwording.data.inScope: yes = passport required; no = none required AND none planned (incl. ESPR-framework-only products, packaging): never say 'not yet' or 'yet'; pending = none today, a passport act is planned: name it fromplanned[]; depends = unanswered facts.ruleStatus: 'needs_recheck': the law behind the act changed and our rules are being re-checked (sincerecheckSince); say so.
Actions (pass via action; {…} is the args object); values, caps and response shapes: resource tracepass://reference/scope.
check — { category?, facts?, role?, placedOnMarket?, lifecycleEvent?, contains?, productId?, passportId?, locale? }. Every plan; counts against the scope-answer cap (~100/day), not the v1 budget (429
scope_answer_cap). Unknownfactskeys: 400. Omitrolefor all roles' duties.catalogue_report — { classification?, category?, act?, changed?, q?, cursor?, limit? (≤500) }. One row per product. Growth plan or above; 403
plan_upgrade_requiredbelow it — tell the user this needs a plan upgrade, do not retry.catalogue_run — {}. Start a refresh run (also nightly); poll with catalogue_run_status. Growth plan. 409 run_in_progress; 429 run_cooldown.
catalogue_run_status — { runId }. Growth plan.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
tracepass_templatesTracePass DPP templates (regulatory schemas)ARead-onlyIdempotentInspect
What a COMPLIANT passport must contain per category, per the governing EU regulation. Read-only reference data; use it to advise on requirements before creating products/passports and to gap-check a draft.
Actions (pass via action; {…} is the args object):
list — {}. All 13 categories with counts and governing regulation.
get — { category }. Every field: key, label, dataType, REQUIRED flag, access level, options, bounds and, where known, the mandating article.
BATTERY — required alone is the wrong answer. SCOPE FIRST: only EV, LMT and industrial_gt_2kwh batteries owe a passport (Art. 77(1), Reg (EU) 2023/1542); for portable, SLI or industrial_lte_2kwh NO field is required — say it is out of scope and list no mandatory fields. Then use requiredBy[batteryCategory] (required | conditional | notApplicable), and required only as a fallback; skipping the scope step invents an obligation the Regulation does not impose. conditional fields, use data and the EV/LMT state-of-health split: resource tracepass://reference/templates.
Inputs: action (required), args. Returns: id, page, error, items, +5 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
The nine top-level tools map to largely distinct TracePass domains: products, passports, lifecycle operations, access grants, EPCIS, field updates, parties, scope, and templates. Some care is needed to distinguish registry-preparation actions inside `tracepass_passports` from registration/lifecycle actions in `tracepass_passport_lifecycle`, and passport field edits from passport creation, but the descriptions make these boundaries workable.
All tool names use the same `tracepass_` prefix, snake_case formatting, and resource-noun pattern. Action names within tools are also consistently verb-like and predictable; minor singular/acronym differences like `tracepass_scope` and `tracepass_epcis` do not disrupt the pattern.
Nine top-level tools is a well-scoped count for a broad DPP platform. Each tool corresponds to a meaningful resource or workflow area, even though `tracepass_passports` is action-heavy and must expose many related operations.
Coverage is very comprehensive: product catalogue management, passport creation/read/compliance/registry readiness, lifecycle transitions, access grants, EPCIS capture/query/export, field and party updates, scope checks, and templates. Publishing appears intentionally dashboard-only rather than missing, and I see no major dead ends in the core domain.
Maintenance
Related MCP Connectors
EPCIS 2.0 repository: trace products, query and count events, resolve GS1 Digital Links.
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
MCP server for Product Management
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Related MCP Servers
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for French Electronic Invoicing (NF XP Z12-013). Provide tools to validate, generate, and explore API specifications for PDP/OD interoperability.341Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.MIT
- AlicenseNot gradedqualityDmaintenanceA hosted remote MCP server for verifying C2PA intakes, classifying source risk, issuing media receipts, and exporting intake logs. Designed for AI governance, trust and safety, and compliance teams.MIT
- AlicenseAqualityBmaintenanceMCP server for GoCertius: certified evidence, dossiers, notifications and chats via AI agents.4175 npmMIT