Trade Compliance
NPM · @PIPEWORX/MCP-TRADE-COMPLIANCE · 2 COMPONENTS
Trade Compliance MCP — the two questions an importer asks that the tariff schedule alone cannot…
Available components
Last scanned (6 hours ago)
Scores higher than 61% of npm servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-trade-compliance). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-trade-compliance@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-trade-compliance |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-trade-compliance/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560509332 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7cfeb0aab2d263ca97634f48aa12dfbf03d2407e34e67f7472627084e33ade0a3ef60472fe3bf316821a084b4a5ef517fa766019b5be5332b451b1311 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
adcvd_case ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
adcvd_orders ~340
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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" |
No output schema declared.
No examples provided.
cross_ruling ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | number|string | – | Truncate the ruling text to this many characters (default 12000, max 60000). Ruling letters run long. |
| ruling_number | string | yes | CROSS ruling number, e.g. "N305619". Get one from cross_search. |
No output schema declared.
No examples provided.
cross_search ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-trade-compliance
claude mcp add pipeworx-io-trade-compliance -- npx -y @pipeworx/mcp-trade-compliance
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.