Skip to main content
Glama

TracePass DPP Compliance Assistant

Server Details

Answers EU Digital Product Passport questions: scope, required fields, registry and law changes.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
malinoto/tracepass-mcp-server
GitHub Stars
1
Server Listing
tracepass-mcp-server
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct intent: profile CRUD, scope determination, required data fields, registry/technical guidance, change tracking, passport drafting, and answer reporting. The closest pair is registry_guidance vs required_fields (data formats/models vs required field list) and registry_guidance vs scope_check, but the descriptions explicitly route between them. Boundaries are mostly clear, with only slight conceptual overlap on 'passport data' topics.

Naming Consistency3/5

Half the tools follow a verb_noun pattern (create_draft_passport, delete_profile, get_profile, update_profile, report_answer, scope_check), while registry_guidance, required_fields, and what_changed are noun or question-style names. All are snake_case and readable, so the convention is mixed but not chaotic. No consistent prefix/namespace ties the set together.

Tool Count5/5

Nine tools is well within the sweet spot and each earns its place: a small profile CRUD group, three knowledge/query tools, a drafting tool, a change feed, and a feedback tool. Nothing appears redundant or padding.

Completeness4/5

The surface covers the core compliance lifecycle: determine scope, learn required fields, understand registry/technical requirements, draft a passport, track changes, and report bad answers, plus profile persistence. Publishing is deliberately user-side and stated as such, but there is no tool to retrieve or list the user's existing passports, and no general article/regulation lookup beyond the fixed query tools—minor gaps an agent can work around.

Available Tools

9 tools
create_draft_passportCreate a draft passportAInspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: category (required), productName (required), gtin, subType, +1 more.

delete_profileDelete all stored company factsA
DestructiveIdempotent
Inspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: no named parameters.

get_profileRead stored company factsA
Read-onlyIdempotent
Inspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: no named parameters.

registry_guidanceEU DPP Registry guidanceA
Read-onlyIdempotent
Inspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: topic (required), locale, category.

report_answerReport a wrong or unclear answerBInspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: what (required), ruleIds.

required_fieldsList required passport fieldsA
Read-onlyIdempotent
Inspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: category (required), group, locale, subType.

scope_checkCheck if a product needs a passportA
Read-onlyIdempotent
Inspect

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 yes (a passport is required), no (none required and none planned, or only the ESPR framework applies; packaging has no passport act), pending (none today, but a passport act is planned: data.planned names it) or depends (on unanswered facts). 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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: role, facts, locale, category, +1 more.

update_profileSave or correct company factsA
DestructiveIdempotent
Inspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: role, markets, ownBrand, products, +4 more.

what_changedWhat changed in EU passport lawA
Read-onlyIdempotent
Inspect

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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

Inputs: since, locale, categories.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables users to determine whether an undertaking is in scope of the EU CSRD and from which financial year, returning a cited chain of rules and flagging issues that depend on national law. It runs offline and can show the article behind each scope step.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables users to search and monitor European regulatory publications including GDPR, ISO27001, and AI Act. Supports creating monitoring topics, generating compliance briefs, and setting up notifications for regulatory updates.
      5
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Query 37 EU regulations — from GDPR and AI Act to DORA, MiFID II, eIDAS, Medical Device Regulation, and more — directly from Claude, Cursor, or any MCP-compatible client.
      14
      25
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Automated EU compliance & recall screening engine under the General Product Safety Regulation (GPSR / EU 2023/988). Features: * Instant Batch EAN/GTIN validation (up to 500 barcodes) with Modulo-10 checksum pre-screening * Real-time indexing against official European Commission Safety Gate (RAPEX) recall alerts * REACH & chemical hazard detection (phthalates, lead, cadmium, toxic substances)
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.