# Trade Compliance (npm · @pipeworx/mcp-trade-compliance)

Trade Compliance MCP — the two questions an importer asks that the tariff schedule alone cannot…

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-trade-compliance/trade-compliance-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-trade-compliance/trade-compliance-mcp)
- npm · `@pipeworx/mcp-trade-compliance`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-trade-compliance/pipeworx-mcp-trade-compliance.md), [page](https://verifymcp.io/servers/pipeworx-io-trade-compliance/pipeworx-mcp-trade-compliance)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-trade-compliance`
- Version: `0.2.0`
- Transport: `stdio`

## 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-trade-compliance).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 986 tokens (~246/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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: 1 category.** A category scored 0 because we could not verify it: 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 Trade Compliance MCP server?

Trade Compliance runs locally as an npm package, launched with npx -y @pipeworx/mcp-trade-compliance. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-trade-compliance -- npx -y @pipeworx/mcp-trade-compliance
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-trade-compliance": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-trade-compliance"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-trade-compliance": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-trade-compliance"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-trade-compliance -- npx -y @pipeworx/mcp-trade-compliance
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-trade-compliance": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-trade-compliance"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-trade-compliance --command npx --arg -y --arg @pipeworx/mcp-trade-compliance
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-trade-compliance:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-trade-compliance"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-trade-compliance": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-trade-compliance"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-trade-compliance -t stdio -c npx -a -y @pipeworx/mcp-trade-compliance
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-trade-compliance": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-trade-compliance"
      ]
    }
  }
}
```

## 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 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `cross_search` (~243 tokens)

Search CBP CROSS — the US Customs and Border Protection ruling letters database — for how Customs has classified a product before. Returns binding and informational ruling letters with ruling number, date, subject, HTS tariff numbers assigned, and whether the ruling was later modified or revoked. Use this to find tariff classification precedent for an import: what HTS code CBP assigned to a similar article, country-of-origin and marking determinations, USMCA/NAFTA eligibility rulings, and valuation rulings. Search by product description ("lithium ion battery pack", "cotton knit shirt"), by HTS code, or by ruling number.

Input parameters:

- `hts` (string): Optional HTS/tariff number to narrow the search, e.g. "8507.60.0020".
- `limit` (number|string): Max rulings to return (1-50, default 20).
- `query` (string, required): Product description, HTS code, or ruling number, e.g. "lithium ion battery pack" or "8507.60".
- `since` (string): Only rulings issued on or after this date (YYYY-MM-DD).

### `cross_ruling` (~167 tokens)

Get one CBP CROSS customs ruling letter in full by its ruling number (e.g. "N305619" or "H301481", from cross_search). Returns the complete ruling text — the facts presented, CBP's classification analysis, and the holding — plus the HTS tariff numbers assigned, issue date, and the rulings it modifies, revokes, or is revoked by. Use this to read the actual reasoning behind a tariff classification precedent before relying on it for an entry.

Input parameters:

- `max_chars` (number|string): Truncate the ruling text to this many characters (default 12000, max 60000). Ruling letters run long.
- `ruling_number` (string, required): CROSS ruling number, e.g. "N305619". Get one from cross_search.

### `adcvd_orders` (~340 tokens)

US antidumping duty (AD) and countervailing duty (CVD) trade-remedy orders — is there an import duty order in place on a product from a country. Searches Federal Register / International Trade Administration notices for a product and/or country, resolves current status per product-country pair (in_place, in_place_revoked_in_part when Commerce revoked an order only for named companies or a carved-out subset, or revoked), and returns AD/CVD case numbers, order type (antidumping, countervailing, or both), and the governing Federal Register notice. Use for "is there an antidumping/countervailing duty order on X from Y", "AD/CVD case number for X", "trade remedy duties on imports of X from Y", "is the dumping order on X still in place". Country matching is forgiving (pass "China", not "the People's Republic of China"). If an HTS code is passed it is used only as a search hint — the ORDER SCOPE LANGUAGE, not any HTS number, governs what merchandise is actually covered, so an HTS mismatch never means "not covered".

Input parameters:

- `country` (string): Country of origin, e.g. "China", "Vietnam", "South Korea" — plain names work
- `hts` (string): Optional HTS/HS code as an additional search hint (advisory only — see description)
- `limit` (number|string): Max product/country groups to return (1-50, default 20)
- `product` (string): Product keyword(s), e.g. "steel", "solar cells", "shrimp"

### `adcvd_case` (~181 tokens)

Look up a specific US antidumping/countervailing duty case by its case number (A-570-979 style: letter A=antidumping or C=countervailing, 3-digit country code, 3-digit case code) or by a Federal Register document number. Returns every Federal Register notice on file for that case with full abstract text and the FR URL — use after adcvd_orders when you already have the case number and need the underlying notices (initiation, order, continuation, revocation, amendments) in one place.

Input parameters:

- `case_number` (string): AD/CVD case number, e.g. "A-570-979" or "C-570-980"
- `document_number` (string): Federal Register document number, e.g. "2026-16033" (alternative to case_number)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-trade-compliance/pipeworx-mcp-trade-compliance#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Trade Compliance MCP server?

Trade Compliance is an MCP server listed in the public MCP registry as io.github.pipeworx-io/trade-compliance. Trade Compliance MCP, the two questions an importer asks that the tariff schedule alone cannot… This page covers its npm package (@pipeworx/mcp-trade-compliance).

### Is the Trade Compliance MCP server safe to use?

Trade Compliance scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Trade Compliance MCP server expose?

Trade Compliance exposes 4 tools: cross_search, cross_ruling, adcvd_orders, adcvd_case. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.

### Is the Trade Compliance MCP server still maintained?

Trade Compliance is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Trade Compliance MCP server under?

Trade Compliance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-trade-compliance
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-trade-compliance
- Repository: https://github.com/pipeworx-io/mcp-trade-compliance
- Website: https://pipeworx.io/packs/trade-compliance
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-trade-compliance/pipeworx-mcp-trade-compliance.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-trade-compliance/pipeworx-mcp-trade-compliance.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-trade-compliance/pipeworx-mcp-trade-compliance