Bragproof

← Reports

tracepass-mcp-server

Starts with no setup1.26.2npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Contacts while installing and starting: nothing

8tools listed
0hosts contacted
0files written
0.2 sto start
95dependencies

Its tool definitions changed since version 1.25.2. If you approved the earlier ones, read them again.

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y tracepass-mcp-server@1.26.2

Installing a package runs its code. Use a sandbox for anything you have not read.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

5 tools with commands in capitals or very long text
  • Gives the agent orders in tracepass_passports: d 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 th
  • Very long description in tracepass_passports: 3000 characters or more
  • Gives the agent orders in tracepass_scope: 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'. -
  • Gives the agent orders in tracepass_passport_lifecycle: s 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
  • Very long description in tracepass_passport_lifecycle: 3000 characters or more

Common and usually harmless: it is how many makers stress how a tool should be used.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

tracepass_products action, args
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? }. `category` is one of the 13 DPP categories (tracepass_templates list).
- update — { id, name?, model?, description? }; at least one field.
- 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).
tracepass_passports action, args
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 `xml` on 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) }.
- list_snapshots — { id, page?, limit?, at? (ISO 8601) }; get_snapshot — { id, snapshotId }. EN 18221 change archive (`at` = the snapshot valid then). 1 read 
tracepass_passport_fields action, args
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? }. `value` type 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`.
tracepass_passport_parties action, args
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.
tracepass_epcis action, args
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.
tracepass_templates action, args
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.
tracepass_scope action, args
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_covered` rests 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_covered` and `needs_input` as results, never errors. `needs_input` = blocking questions remain — relay `ask[]` to the user before giving a verdict.
- Items in an act's `planned` list are not law yet: label them 'Planned, not law yet' (`labelText`), with their `wording`.
- `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 from `planned[]`; depends = unanswered facts.
- `ruleStatus: 'needs_recheck'`: the law behind the act changed and our rules are being re-checked (since `recheckSince`); 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`). Unknown `facts` keys: 400. Omit `role` for all roles' duties.
- catalogue_report — { classification?, category?, act?, changed?, q?, cursor?, limit? (≤500) }. One row per product. Growth plan or above; 403 `plan_upgrade_required` below 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.
tracepass_passport_lifecycle action, args
WARNING: Every action here changes what the public sees or is a legal act, some irreversible. `archive` permanently removes the public QR code (it 404s forever). `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. The public QR permanently 404s. reason is REQUIRED for battery passports (400 reason_required): recycled, never_placed

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=20
Sourcegithub.com/malinoto/tracepass-mcp-server
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-yQM8khOcfqXd7/O9Ghra8CAD0ZLVhw62KBimxPB4wH0ZKF5E/p3RSzjK1fnafmK5J/FpbETZQJ2rg/fzN9Cb4A==

Versions reported

VersionRunResultTools
1.26.22026-11-16Starts with no setup8
1.25.22026-11-12Starts with no setup8

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/tracepass-mcp-server.svg)](https://bragproof.smaverk.com/r/tracepass-mcp-server)

New version out? Ask for a fresh report.