# WISEPIM Commerce Reference (mcpb · wisepim-commerce.mcpb)

Offline HS heading lookup, marketplace listing requirements and EU green-claims screening.

- Trust score: 33/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `wisepim-commerce.mcpb`: 33/100 (this document), [markdown](https://verifymcp.io/servers/lldiegon-wisepim-commerce-mcp/wisepim-commerce.md), [page](https://verifymcp.io/servers/lldiegon-wisepim-commerce-mcp/wisepim-commerce)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/lldiegon/wisepim-commerce-mcp/releases/download/v1.0.0/wisepim-commerce.mcpb`
- Transport: `stdio`
- SHA-256: `9594473e12d302f15e54cfb6221302b0fb79376e30b3e978a3f4f889b5641f97`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 136 tokens (~45/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the WISEPIM Commerce Reference MCP server?

WISEPIM Commerce Reference ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 9594473e12d302f15e54cfb6221302b0fb79376e30b3e978a3f4f889b5641f97; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/lldiegon/wisepim-commerce-mcp/releases/download/v1.0.0/wisepim-commerce.mcpb`
- SHA-256: `9594473e12d302f15e54cfb6221302b0fb79376e30b3e978a3f4f889b5641f97`

### Verify on macOS / Linux

```bash
echo "9594473e12d302f15e54cfb6221302b0fb79376e30b3e978a3f4f889b5641f97  wisepim-commerce.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\wisepim-commerce.mcpb).Hash -eq "9594473e12d302f15e54cfb6221302b0fb79376e30b3e978a3f4f889b5641f97"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 33)

First indexed and scored.

## MCP tools (3)

### `lookup_hs_heading` (~45 tokens)

Find EU CN 2026 chapters and four-digit headings by exact code or English description keywords. Returns up to 25 candidates for review.

Input parameters:

- `query` (string, required)

### `marketplace_requirements` (~37 tokens)

Read the WISEPIM listing-field checklist for one marketplace, including required fields, formats and examples.

Input parameters:

- `marketplace` (string, required)

### `check_green_claims` (~54 tokens)

Flag environmental claims in product copy for human review under Directive (EU) 2024/825. Phrase matching cannot assess evidence or establish legal compliance.

Input parameters:

- `language` (string)
- `text` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lldiegon-wisepim-commerce-mcp/wisepim-commerce#diagnostics

## Score history

- 2026-11-05: 33
- 2026-11-04: 33
- 2026-11-03: 33
- 2026-11-02: 33

## Common questions

### What is the WISEPIM Commerce Reference MCP server?

WISEPIM Commerce Reference is an MCP server listed in the public MCP registry as io.github.lldiegon/wisepim-commerce-mcp. Offline HS heading lookup, marketplace listing requirements and EU green-claims screening. This page covers its MCPB bundle (https://github.com/lldiegon/wisepim-commerce-mcp/releases/download/v1.0.0/wisepim-commerce.mcpb).

### Is the WISEPIM Commerce Reference MCP server safe to use?

WISEPIM Commerce Reference scores 33 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 WISEPIM Commerce Reference MCP server expose?

WISEPIM Commerce Reference exposes 3 tools: lookup_hs_heading, marketplace_requirements, check_green_claims. Their descriptions and schemas cost roughly 136 tokens of context every time the server is loaded.

### What did VerifyMCP test on the WISEPIM Commerce Reference MCP server?

VerifyMCP ran 11 checks on WISEPIM Commerce Reference, covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about WISEPIM Commerce Reference: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/lldiegon/wisepim-commerce-mcp
- Changelog RSS feed: https://verifymcp.io/servers/lldiegon-wisepim-commerce-mcp/wisepim-commerce.xml
- Changelog JSON feed: https://verifymcp.io/servers/lldiegon-wisepim-commerce-mcp/wisepim-commerce/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lldiegon-wisepim-commerce-mcp/wisepim-commerce.json
- HTML version of this page: https://verifymcp.io/servers/lldiegon-wisepim-commerce-mcp/wisepim-commerce
