TracePass DPP Compliance Assistant
REMOTE · AI.TRACEPASS.EU
Answers EU Digital Product Passport questions: scope, required fields, registry and law changes.
Available components
Last scanned (7 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2628 tokens (~292/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 0
- Server version: 1.20.1 → 1.20.2 functional
- Server version: 1.20.0 → 1.20.1 functional
- Server version: 1.19.1 → 1.20.0 functional
- “create_draft_passport” reworded the description of “category” cosmetic
- “required_fields” reworded the description of “category” cosmetic
- “scope_check” reworded the description of “category” cosmetic
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +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.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.19.0 → 1.19.1 functional
- 12 Oct 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://ai.tracepass.eu/compliance/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai.tracepass.eu | CN=YE2,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5391fc7ec73418735df89fea6923bdd6e56 |
| SANs: ai.tracepass.eu | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai.tracepass.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| tracepass.eu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="TracePass DPP Compliance Assistant", error="invalid_token", resource_metadata="https://ai.tracepass.eu/.well-known/oauth-protected-resource/compliance/mcp", error_description="Authenticate with a TracePass API key or via OAuth for the DPP Compliance Assistant (see resource_metadata)."
Bearer realm="TracePass DPP Compliance Assistant", error="invalid_token", resource_metadata="https://ai.tracepass.eu/.well-known/oauth-protected-resource/compliance/mcp", error_description="Authenticate with a TracePass API key or via OAuth for the DPP Compliance Assistant (see resource_metadata)."| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://ai.tracepass.eu/.well-known/oauth-protected-resource/compliance/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://ai.tracepass.eu/compliance/mcp |
| Authorisation server | https://app.tracepass.eu |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.tracepass.eu/compliance/mcp | Verified | 200 | |
| http (plaintext) | http://ai.tracepass.eu/compliance/mcp | HTTPS enforced | 308 | https://ai.tracepass.eu/compliance/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_draft_passport Create a draft passport ~356
Creates a **draft** passport in the user's own TracePass account from facts they stated. Use it whenever the user asks to create a passport, including "create and publish": create the draft, then say that publishing is done by the user in TracePass. It never publishes. If the result asks for an identifier, ask the user; never invent one. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Product category key, one of the listed values. Map the user's product to the closest key (paint → paints-coatings, an e-bike battery → battery). Never pass the user's own words. If none fits, there… |
| gtin | string | – | The product's GTIN (barcode number, 8–14 digits). Required for most passport types. If missing, the tool will ask the user for it. |
| productName | string | yes | The product's name. |
| serialNumber | string | – | The specific unit's serial number, if the passport is per-unit. |
| subType | string | – | Battery only: EV, LMT or industrial_gt_2kwh. Used to count the required fields for that battery type; ask the user rather than guess. |
No output schema declared.
No examples provided.
delete_profile Delete all stored company facts ~139
Deletes every stored company fact. Use it only when the user explicitly asks to delete their profile. This is a separate tool so the assistant asks for confirmation before running it. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_profile Read stored company facts ~133
Shows the company facts the assistant has stored (categories, markets, role, own-brand flag, etc.) and when they were last updated. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
registry_guidance EU DPP Registry guidance ~221
Explains the EU DPP Registry and the technical side: registration in the registry, identifiers, QR and data carriers, data formats (JSON, HTML, data models) and standards, and where passport data is kept. Each point carries the date of its source. For who owes, keeps or may hand off a passport, use scope_check. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g. battery) for category-specific guidance. |
| locale | string | – | Language for the answer. Defaults to en. |
| topic | string | yes | The topic to answer. |
No output schema declared.
No examples provided.
report_answer Report a wrong or unclear answer ~180
Use it when the user says an answer was wrong or unclear. Pass their words and the `ruleIds` of the answer. The report goes to a review queue. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
| Name | Type | Req | Description |
|---|---|---|---|
| ruleIds | array | – | The ruleIds from the answer that was reported. Pass them from the result unchanged. |
| what | string | yes | The user's own words describing what was wrong or unclear. |
No output schema declared.
No examples provided.
required_fields List required passport fields ~323
Lists the data a passport must contain for a product category, with the article requiring each field, who may see it, how often it changes, and whether it usually comes from the maker or a supplier. Call it without `group` for a summary (counts by group), then with a `group` for the fields. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Product category key, one of the listed values. Map the user's product to the closest key (paint → paints-coatings, an e-bike battery → battery). Never pass the user's own words. If none fits, there… |
| group | string | – | Template group name. Omit for a summary; provide to list the fields. |
| locale | string | – | Language for field labels and descriptions. Defaults to en. |
| subType | string | – | Battery only: EV, LMT or industrial_gt_2kwh (an industrial battery over 2 kWh). Narrows the required fields to that battery type; an unknown value is refused with the allowed list. |
No output schema declared.
No examples provided.
scope_check Check if a product needs a passport ~442
Checks whether EU law requires a Digital Product Passport for a type of product, from when, and what the law requires of each role. Use it for "do I need a passport", "from when", "who is responsible", whether that responsibility can be handed to another company, who keeps and stores the passport and whether it must stay available after the company ceases, whether there is one passport per item, batch or model, and for repurposing, remanufacturing, waste or a battery inside another product. Pass whatever facts the user gave; if the result is needs_input, ask the user its questions in plain words and call again. The result's data.inScope is one of: yes, no, pending, depends. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Product category key, one of the listed values. Map the user's product to the closest key (paint → paints-coatings, an e-bike battery → battery); use "other" when no key fits. Never pass the user's o… |
| facts | object | – | Product facts the scope rules declare, e.g. {"battery.capacityKWh": 10}. Any other key is rejected, so pass only a fact you know the rules use (such as one a needs_input result asked for), and never… |
| locale | string | – | Language for the answer text. Defaults to en. |
| placedOnMarket | object | – | When the product was or will be placed on the market. |
| role | string | – | The user's role in plain words, e.g. "maker", "importer", "reseller". The platform maps this to the act's term. |
No output schema declared.
No examples provided.
update_profile Save or correct company facts ~322
Saves or corrects company facts. Use it when the user states a lasting fact about their company (role, categories, markets, own-brand), or to save a `learnable` fact from a result. The update merges the given facts into the existing profile; it does not replace the whole profile. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Product categories the company handles, e.g. ["battery", "textile"]. |
| dataSystems | string | – | Short description of the data systems the company uses (e.g. SAP, custom ERP). |
| markets | array | – | ISO country codes where the company sells, or ["EU"]. |
| ownBrand | boolean | – | True if the company sells under its own brand or trademark. |
| products | array | – | Up to 50 representative products, used as defaults for passport creation. |
| role | string | – | The company's role in the supply chain per EU DPP regulations. |
| salesChannels | array | – | Sales channels the company uses. |
| sizeBand | string | – | Whether the company is an SME or a large enterprise. |
No output schema declared.
No examples provided.
what_changed What changed in EU passport law ~227
Reports changes in EU passport law and standards for the user's categories since a date (default: since they last asked). Use it for "what's new" or "has X been adopted". Items marked "Planned, not law yet" are upcoming obligations, not yet in force. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Product categories to filter by. Defaults to the saved profile categories. |
| locale | string | – | Language for summaries. Defaults to en. |
| since | string | – | ISO date to look back from. Defaults to the date this account last called what_changed (first time: 90 days ago). |
No output schema declared.
No examples provided.
How do I install the TracePass DPP Compliance Assistant MCP server?
TracePass DPP Compliance Assistant is a hosted endpoint at https://ai.tracepass.eu/compliance/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai.tracepass.eu
claude mcp add --transport http eu-tracepass-compliance 'https://ai.tracepass.eu/compliance/mcp'
What is the TracePass DPP Compliance Assistant MCP server?
TracePass DPP Compliance Assistant is an MCP server listed in the public MCP registry as eu.tracepass/compliance. Answers EU Digital Product Passport questions: scope, required fields, registry and law changes. This page covers its hosted endpoint (https://ai.tracepass.eu/compliance/mcp).
Is the TracePass DPP Compliance Assistant MCP server safe to use?
TracePass DPP Compliance Assistant scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TracePass DPP Compliance Assistant MCP server expose?
TracePass DPP Compliance Assistant exposes 9 tools: scope_check, required_fields, what_changed, registry_guidance, create_draft_passport, and 4 more. Their descriptions and schemas cost roughly 2,343 tokens of context every time the server is loaded.
Does the TracePass DPP Compliance Assistant MCP server require authentication?
Yes. TracePass DPP Compliance Assistant asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the TracePass DPP Compliance Assistant MCP server still maintained?
TracePass DPP Compliance Assistant is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.