Skip to content

TracePass DPP Compliance Assistant MCP server

eu.tracepass/compliancetracepass.eustreamable-httpv1.28.0Scanned

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

9 tools: 2 can delete or cancel things, 4 change things and 3 only read.

Tools: 2 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TracePass DPP Compliance Assistant MCP server can do

The TracePass DPP Compliance Assistant MCP server is published by tracepass.eu, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (2 tools: update_profile and delete_profile) and create or change data (4 tools: scope_check, what_changed, create_draft_passport and report_answer). 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.28.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 2Claude Code: deny
  • delete_profileDeletes every stored company fact.No findings

    Why it is in this group

    • The name "delete_profile" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • update_profileSaves or corrects company facts.No findings

    Why it is in this group

    • The name "update_profile" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 4Claude Code: ask
  • create_draft_passportCreates a **draft** passport in the user's own TracePass account from facts they stated.No findings

    Why it is in this group

    • The name "create_draft_passport" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • report_answerUse it when the user says an answer was wrong or unclear.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • scope_checkChecks whether EU law requires a Digital Product Passport for a type of product, from when, and what the law requires of each role.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • what_changedReports changes in EU passport law and standards for the user's categories since a date (default: since they last asked).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_profileShows the company facts the assistant has stored (categories, markets, role, own-brand flag, etc.) and when they were last updated.No findings

    Why it is in this group

    • The name "get_profile" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • registry_guidanceExplains 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 wher…No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • required_fieldsLists 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 ma…No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://ai.tracepass.eu/.well-known/oauth-protected-resource/compliance/mcp
Authorization servers
https://app.tracepass.eu
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (2 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ai.tracepass.eu/compliance/mcp: tools/list returned 9 tools to an anonymous client, including update_profile (destructive), delete_profile (destructive), scope_check (write), what_changed (write), create_draft_passport (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Client ID metadata documents: no to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Client ID metadata documents: no -> yes.View diff
    • Client ID metadata documents: no to yes
  2. Tools1 changed.~1 changedView diff
  3. Tools9 changed.~9 changedView diff
  4. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.28.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http compliance https://ai.tracepass.eu/compliance/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http compliance https://ai.tracepass.eu/compliance/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__compliance__required_fields",
      "mcp__compliance__registry_guidance",
      "mcp__compliance__get_profile"
    ],
    "ask": [
      "mcp__compliance__scope_check",
      "mcp__compliance__what_changed",
      "mcp__compliance__create_draft_passport",
      "mcp__compliance__report_answer"
    ],
    "deny": [
      "mcp__compliance__update_profile",
      "mcp__compliance__delete_profile"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as compliance. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/eu.tracepass/compliance/verify?hash=611ec1ce9bae02cfa83d56684cea61d770d94d337d5b6a40d534db547edd0b8e" | jq -e '.changed == false'

Pinned hash 611ec1ce9bae, from Nov 17, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/eu.tracepass/compliance/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for eu.tracepass/compliance
[![Anlyon Radar](https://radar.anlyon.com/badge/eu.tracepass/compliance.svg)](https://radar.anlyon.com/servers/eu.tracepass/compliance)

Source: MCP Registry · repository. Synced Nov 17, 2026, 19:17 UTC.

TracePass DPP Compliance Assistant MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TracePass DPP Compliance Assistant MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TracePass DPP Compliance Assistant MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: update_profile and delete_profile.

Can the TracePass DPP Compliance Assistant MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TracePass DPP Compliance Assistant MCP server have?

9 tools: 2 destructive, 4 write, 3 read. update_profile, delete_profile, scope_check, what_changed, create_draft_passport, report_answer, required_fields, registry_guidance and 1 more.

Does the TracePass DPP Compliance Assistant MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TracePass DPP Compliance Assistant MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the TracePass DPP Compliance Assistant MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.