Compliance

com.yaktoolPublished by yaktool.comv0.4.0Updated Oct 24, 2026

GPSR, EUDR plots, nutrition labels, fragrance allergens, CPSC and EU conformity declarations.

VerifiedSTDIODesktop onlyBusiness & Commerce

Server details

Identifier: com.yaktool/compliance
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to yaktool.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.yaktool%2Fcompliance.svg)](https://sourceweft.com/mcp/com.yaktool%2Fcompliance?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that helps an assistant work with product compliance topics such as GPSR, EUDR plots, nutrition labels, fragrance allergens and conformity…

What you can do: The manifest lists no tools, so capabilities can only be inferred from the registry description.
It is presented as covering GPSR (EU General Product Safety Regulation) matters.
It covers EUDR plots, i.e. geolocation data for EU deforestation regulation.
It covers nutrition labels and fragrance allergen information.
It covers CPSC and EU conformity declarations.
When to use it: Worth considering when you need an assistant to help draft, check or organize product compliance material for EU or US markets, such as safety information, allergen and nutrition labelling, deforestation plot data or conformity declarations.
Requirements: Runs as a local process on the user's machine over stdio, installed from the npm package yaktool-compliance-mcp, so a Node.js runtime is needed. Desktop client only; no web execution. No authentication, environment variables or headers are declared.

Before you install

No tools, README or instructions are published, so what the server actually does and what data it handles cannot be verified before installing. Compliance output may be incomplete or outdated and should be checked against current regulations and official sources; it is not legal advice.

Installation

In SourceWeft

Open Compliance in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.4.0LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.