MCP server for TracePass — the EU Digital Product Passport (DPP) compliance platform for the ESPR and EU Battery Regulation. Lets AI assistants create products, build and audit Digital Product Passports (battery: 91 fields; electronics: 166), set economic-operator parties, and read or capture GS1 EPCIS 2.0 supply-chain events. 6 tools, 2 resources, 5 prompts. Connect to the hosted endpoint (https://ai.tracepass.eu/mcp) with a TracePass tp_ API key, or run locally via npx -y tracepass-mcp-server.

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 1,046 ms, 95th percentile 2,559 ms.

When we called tools/list it returned 8 tools, including tracepass_products, tracepass_passports, tracepass_passport_fields, over MCP protocol revision 2025-11-25.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 28% and higher on readiness than 88%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (8)

As returned by the server's own tools/list when we called it.

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 billa…
tracepass_passports: Manage Digital Product Passports — create, read, and run compliance checks. IMPORTANT: `create` makes a DRAFT passport. A draft takes no plan DPP slot and is n…
tracepass_passport_fields: Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail with the credential that made it (API key or connected…
tracepass_passport_parties: Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each pa…
tracepass_epcis: 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 eve…
tracepass_templates: Discover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the governing EU regulation. Read-only reference data.…
tracepass_scope: 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…
tracepass_passport_lifecycle: 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)…

MCP readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (2521 ms); slow response -1.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 8 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (2521 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-12.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness: Higher than 88% of peers; This listing 87 · peer median 81
Latency: Faster than 28% of peers; This listing 591 ms · peer median 349 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-14 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/malinoto/tracepass-mcp-server/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/malinoto/tracepass-mcp-server/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.tracepass.eu

Listed at (smithery)

https://www.tracepass.eu