Skills/npm/tracepass-mcp-server

tracepass-mcp-server@1.25.2

VERIFIED· not started

Publisher claims: "Model Context Protocol server for TracePass — the EU Digital Product Passport platform. Lets AI assistants manage products, passports, and EPCIS supply-chain events." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher malinoto · publishing for 175 daysInstalls 4,614Last detonated 4d ago
$claude mcp add tracepass-mcp-server -- npx -y tracepass-mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
TRACEPASS_API_KEYConfiguration, not credentials: COMPLIANCE_MCP_PATH, COMPLIANCE_PROTECTED_RESOURCE_METADATA_PATH, MCP_BATCH_LIMIT, MCP_BODY_LIMIT_BYTES, MCP_PATH, PROTECTED_RESOURCE_METADATA_PATH, SUPPLIER_MCP_PATH, VITEST
Where it talks to
tracepass.eu (its own)Also glama.ai, doi.org — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names glama.ai, doi.org as well as its own vendor. The guard injects TRACEPASS_API_KEY only into requests to tracepass.eu (and its subdomains) and refuses the rest.

$vet-skills run --secrets TRACEPASS_API_KEY=tracepass.eu -- npx -y tracepass-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 9 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
9.0sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-i4AEN8/task/home/.npm/_logs/2026-11-10T02_38_55_763Z-debug-0.log
9.0sclaimednot started: dependency install failed (exit 1); the server itself was not observed
9.0sprocessscript backend runs setup only
9.0sprocessno install scripts to re-run

Static findings

HIGH
Credential pass-through configurationdist/http.js:6 · Credential pass-through configuration — agent relays sensitive credentials* Streamable HTTP; the caller's TracePass credential travels in theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
MEDIUM
MCP server using network transport (SSE/HTTP)dist/stdio.js:14 · MCP server using network transport (SSE/HTTP) — data sent over network* This is the SAME server core (`createMcpServer`) the hosted HTTPFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
npx invocation of non-well-known packagedist/stdio.js:3 · npx invocation of non-well-known package — may execute untrusted code* stdio entrypoint — the local / npx form of the TracePass MCPFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
MCP server using network transport (SSE/HTTP)dist/stdio.d.ts:14 · MCP server using network transport (SSE/HTTP) — data sent over network* This is the SAME server core (`createMcpServer`) the hosted HTTPFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
HIGH
Credential pass-through configurationdist/http.d.ts:6 · Credential pass-through configuration — agent relays sensitive credentials* Streamable HTTP; the caller's TracePass credential travels in theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
HIGH
Credential pass-through configurationdist/compliance-server.js:118 · Credential pass-through configuration — agent relays sensitive credentialsreturn errorResult("Authentication failed — the TracePass credential is missing or invalid. Check the API key or re-authorise the assistant.");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
MEDIUM
npx invocation of non-well-known packagedist/stdio.d.ts:3 · npx invocation of non-well-known package — may execute untrusted code* stdio entrypoint — the local / npx form of the TracePass MCPFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈82 tok
1 file · 26 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for tracepass-mcp-server@1.25.2 as of 4d ago. This is the package itself, not its dependencies.