# TracePass (remote · ai.tracepass.eu)

Manage products, EU Digital Product Passports, operator parties, and GS1 EPCIS supply-chain events.

- Trust score: 82/100 (high trust)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ai.tracepass.eu`: 82/100 (this document), [markdown](https://verifymcp.io/servers/eu-tracepass-tracepass/ai.md), [page](https://verifymcp.io/servers/eu-tracepass-tracepass/ai)
- npm · `tracepass-mcp-server`: 44/100, [markdown](https://verifymcp.io/servers/eu-tracepass-tracepass/tracepass-mcp-server.md), [page](https://verifymcp.io/servers/eu-tracepass-tracepass/tracepass-mcp-server)

## Channel facts

- Endpoint: `https://ai.tracepass.eu/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.7.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2052 tokens (~256/item across 8 items; 6 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http eu-tracepass-tracepass https://ai.tracepass.eu/mcp
```

### Codex

```toml
[mcp_servers.eu-tracepass-tracepass]
url = "https://ai.tracepass.eu/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-tracepass-tracepass": {
      "type": "remote",
      "url": "https://ai.tracepass.eu/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-tracepass-tracepass --url https://ai.tracepass.eu/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-tracepass-tracepass:
    url: "https://ai.tracepass.eu/mcp"
```

### Other

```json
{
  "mcpServers": {
    "eu-tracepass-tracepass": {
      "type": "http",
      "url": "https://ai.tracepass.eu/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 80, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 73)

First indexed and scored.

## MCP tools (6)

### `tracepass_products` (~208 tokens)

TracePass products

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.

Actions (pass via `action`, with `args`):
\- list — args: { page?, limit? (≤100), category?, status?, search? }. Read-only.
\- get — args: { id }. Read-only.
\- create — args: { name, model, category, description? }. `category` is one of: battery, textile, electronics, construction, steel, chemicals, packaging, furniture, tyres, jewelry, toys, fmcg.
\- update — args: { id, name?, model?, description? }; pass at least one field to change.

Input parameters:

- `action` (string, required): Which product operation to run: list | get | create | update.
- `args` (object): Arguments for the chosen action; required fields depend on `action` (see each action above).

Output parameters:

- `error` (string): Machine-readable error code, when the API rejected the request.
- `id` (string): The resource's TracePass id, when the response is a single entity.
- `items` (array): The page of results, when the action is a list.
- `limit` (number): Page size (list actions).
- `message` (string): Human-readable error or status detail, when present.
- `page` (number): Current page number (list actions).
- `result`: Wraps a non-object response body (e.g. a QR code string).
- `total` (number): Total matching records across all pages (list actions).
- `totalPages` (number): Total number of pages (list actions).

### `tracepass_passports` (~786 tokens)

TracePass passports

Manage Digital Product Passports — create, read, and run lifecycle actions.

IMPORTANT: `create` consumes a DPP slot on the account's plan and IS BILLABLE. Creating a passport beyond the included quota incurs a per-passport overage charge; if over quota the tool returns a 402-style message — only re-run with args.confirmOverage=true after the user explicitly agrees to the charge. `archive` is IRREVERSIBLE (the public QR permanently 404s); prefer `suspend` when a change might be undone.

Actions (pass via `action`, with `args`):
\- list — args: { page?, limit? (≤100), productId?, status?, search? }. status ∈ draft|in_review|approved|published|suspended|expired|archived. Read-only.
\- get — args: { id, format? (summary|full), lang? }. Read-only.
\- get_by_serial — args: { serial, format?, lang?, gtin? }. Read-only. Addresses the passport by your own serial. A serial is unique only WITHIN a GTIN — if the same serial exists under two GTINs in your account the call returns 409 ambiguous_serial; pass `gtin` (or use the by-id action) to resolve exactly.
\- compliance — args: { id }. Read-only. Returns a three-tier compliance verdict (compliant | compliant_with_warnings | incomplete) with regulation-cited findings — use to gap-check a passport against the rules for its category, fix the cited fields/parties, then re-check.
\- registry_readiness — args: { id }. Read-only. Returns { ready, findings[] } — whether the passport would pass the EU DPP Registry's FORMAL submission gate (mandatory fields present, correct formatting, a resolvable public link, item-level granularity via a serial number, and a well-formed commodity code where the category carries one). This is the registry's mechanical pre-submission check, NOT the substantive compliance verdict; a passport can be registry-ready yet not substantively compliant. Battery passports only.
\- create — args: { productId, gtin, serialNumber, confirmOverage? }. BILLABLE.
\- suspend — args: { id }. Reversible — public QR shows 'suspe…

Input parameters:

- `action` (string, required): Which passport operation to run. Reads: list | get | get_by_serial | compliance | registry_readiness | get_qr | get_qr_by_serial. Lifecycle: create (BILLABLE) | suspend (reversible) | archive (IRREVE…
- `args` (object): Arguments for the chosen action; required fields depend on `action` (see each action above).

Output parameters:

- `error` (string): Machine-readable error code, when the API rejected the request.
- `id` (string): The resource's TracePass id, when the response is a single entity.
- `items` (array): The page of results, when the action is a list.
- `limit` (number): Page size (list actions).
- `message` (string): Human-readable error or status detail, when present.
- `page` (number): Current page number (list actions).
- `result`: Wraps a non-object response body (e.g. a QR code string).
- `total` (number): Total matching records across all pages (list actions).
- `totalPages` (number): Total number of pages (list actions).

### `tracepass_passport_fields` (~201 tokens)

TracePass passport fields

Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update.

Actions (pass via `action`, with `args`):
\- update — args: { id, fieldKey, value }. `value` type matches the field's dataType (string, number, boolean, array, object).
\- update_by_serial — args: { serial, fieldKey, value, gtin? }. Same as update, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass `gtin` (or use update by id) to resolve exactly.

Input parameters:

- `action` (string, required): Update one passport field, addressed by passport id (update) or by your serial (update_by_serial).
- `args` (object): Arguments for the chosen action; required fields depend on `action`.

Output parameters:

- `error` (string): Machine-readable error code, when the API rejected the request.
- `id` (string): The resource's TracePass id, when the response is a single entity.
- `items` (array): The page of results, when the action is a list.
- `limit` (number): Page size (list actions).
- `message` (string): Human-readable error or status detail, when present.
- `page` (number): Current page number (list actions).
- `result`: Wraps a non-object response body (e.g. a QR code string).
- `total` (number): Total matching records across all pages (list actions).
- `totalPages` (number): Total number of pages (list actions).

### `tracepass_passport_parties` (~156 tokens)

TracePass passport parties

Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and ideally a validated 13-digit GS1 GLN.

Actions (pass via `action`, with `args`):
\- set — args: { id, role, legalName, gln?, country?, legacyOperatorId? }. Sets or updates one role.
\- remove — args: { id, role }. Clears one role.

Input parameters:

- `action` (string, required): Set (add/replace) or remove an economic-operator party on a passport by its role.
- `args` (object): Arguments for the chosen action; required fields depend on `action`.

Output parameters:

- `error` (string): Machine-readable error code, when the API rejected the request.
- `id` (string): The resource's TracePass id, when the response is a single entity.
- `items` (array): The page of results, when the action is a list.
- `limit` (number): Page size (list actions).
- `message` (string): Human-readable error or status detail, when present.
- `page` (number): Current page number (list actions).
- `result`: Wraps a non-object response body (e.g. a QR code string).
- `total` (number): Total matching records across all pages (list actions).
- `totalPages` (number): Total number of pages (list actions).

### `tracepass_epcis` (~328 tokens)

TracePass EPCIS 2.0

GS1 EPCIS 2.0 supply-chain events. `export` is included on Starter plans and up; `capture`, `capture_job`, and `query` require the paid EPCIS add-on (those actions return a 403-style message without it).

Actions (pass via `action`, with `args`):
\- export — args: { id }. Export a passport's events as an EPCIS 2.0 JSON-LD document. Read-only.
\- export_by_serial — args: { serial, gtin? }. Same as export, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass `gtin` (or use export by id). Read-only.
\- capture — args: { events }. `events` is an EPCISDocument, a single event, or an array of events (JSON-LD). Returns a 202 with a captureJobId.
\- capture_job — args: { jobId }. Poll an async capture job. Read-only.
\- query — args: { params? }. `params` is a key/value map of standard EPCIS query parameters (EQ_bizStep, GE_eventTime, MATCH_epc, …). Read-only.

Input parameters:

- `action` (string, required): EPCIS 2.0: export a passport's events (export | export_by_serial), capture new events, poll a capture job, or query events.
- `args` (object): Arguments for the chosen action; required fields depend on `action`.

Output parameters:

- `error` (string): Machine-readable error code, when the API rejected the request.
- `id` (string): The resource's TracePass id, when the response is a single entity.
- `items` (array): The page of results, when the action is a list.
- `limit` (number): Page size (list actions).
- `message` (string): Human-readable error or status detail, when present.
- `page` (number): Current page number (list actions).
- `result`: Wraps a non-object response body (e.g. a QR code string).
- `total` (number): Total matching records across all pages (list actions).
- `totalPages` (number): Total number of pages (list actions).

### `tracepass_templates` (~246 tokens)

TracePass DPP templates (regulatory schemas)

Discover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the governing EU regulation. Read-only reference data. Use this to advise on requirements before creating products/passports, and to gap-check a draft against the rules.

Actions (pass via `action`, with `args`):
\- list — args: {}. Lists all 12 categories with their field count, required-field count, and governing regulation (name + number + effective/mandatory dates).
\- get — args: { category }. Full field schema for one category: every field's key, label, dataType, whether it is REQUIRED, its access level (public/restricted/authority), enum options, validation bounds, and — where known — the regulation article/annex that mandates it. `category` is one of: battery, textile, electronics, construction, steel, chemicals, packaging, furniture, tyres, jewelry, toys, fmcg.

Input parameters:

- `action` (string, required): List all DPP category templates, or get one template by category.
- `args` (object): Arguments for the chosen action; `category` is required for get, ignored for list.

Output parameters:

- `error` (string): Machine-readable error code, when the API rejected the request.
- `id` (string): The resource's TracePass id, when the response is a single entity.
- `items` (array): The page of results, when the action is a list.
- `limit` (number): Page size (list actions).
- `message` (string): Human-readable error or status detail, when present.
- `page` (number): Current page number (list actions).
- `result`: Wraps a non-object response body (e.g. a QR code string).
- `total` (number): Total matching records across all pages (list actions).
- `totalPages` (number): Total number of pages (list actions).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eu-tracepass-tracepass/ai#diagnostics

## Score history

- 2026-08-03: 82
- 2026-08-02: 81
- 2026-08-01: 81
- 2026-07-31: 80
- 2026-07-30: 75
- 2026-07-29: 75
- 2026-07-28: 74
- 2026-07-27: 74
- 2026-07-26: 73

## Links

- Remote endpoint: https://ai.tracepass.eu/mcp
- Authorisation metadata: https://ai.tracepass.eu/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/malinoto/tracepass-mcp-server
- Website: https://www.tracepass.eu/
- Changelog RSS feed: https://verifymcp.io/servers/eu-tracepass-tracepass/ai/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-tracepass-tracepass/ai/changelog.json
- HTML version of this page: https://verifymcp.io/servers/eu-tracepass-tracepass/ai