Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Japan Tariff

NPM · @PIPEWORX/MCP-JAPAN-TARIFF · 2 COMPONENTS

Japan Tariff — Japan's customs tariff schedule (実行関税率表) by HS code.

68 Trust /100

Last scanned (14 hours ago)

Scores higher than 39% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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 & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 540 tokens (~270/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 53

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@pipeworx/mcp-japan-tariff@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~483 tokens

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 →

Tool Tokens
jp_tariff_lookup ~292

Look up Japan's applied customs tariff rates by HS code: the line description and the general, temporary, WTO, GSP and LDC duty rates, the rate under each economic partnership agreement (CPTPP, EU, UK, RCEP, ASEAN, Australia, India, Switzerland and others, plus the JP-US trade agreement) and the quantity units. Accepts a 2-digit chapter, 4-digit heading (e.g. 0713 dried legumes), 6-digit subheading or 9-digit statistical code, with or without dots; a longer foreign code is cut to its first 6 digits. Answers 'what duty does Japan charge on this HS code', 'Japan import tariff on X', 'Japan EPA preferential rate for Y'. Returns the schedule edition date; an unknown code returns found:false.

NameTypeReqDescription
hs_codestringyesHS code, 2 to 9 digits, dots optional (e.g. "0713", "0713.32", "071332010"). Codes longer than 9 digits are cut to 6.
limitnumber–Maximum lines to return (default 25, max 100).
partnerstring–Optional trade-agreement partner to keep in epa_rates, e.g. "cptpp", "eu", "uk", "india", "rcep", "viet_nam", "australia".

No output schema declared.

No examples provided.

jp_tariff_search ~191

Search Japan's customs tariff schedule by product keyword (English) and get the matching HS lines with their headline duty rates (general, WTO, GSP, LDC). Use it to find which HS code and duty rate Japan applies to a product such as beans, green tea, lithium batteries, wine or cotton fabric, then call jp_tariff_lookup for every partnership rate. Optional chapter (1-97) limits the search to one HS chapter. Returns the schedule edition date; no match returns found:false with a hint.

NameTypeReqDescription
chapternumber–Optional HS chapter 1-97 to search within (rates then come from that chapter live).
keywordstringyesProduct words in English, e.g. "adzuki beans", "green tea", "lithium battery". All words must appear.
limitnumber–Maximum matches (default 10, max 30).

No output schema declared.

No examples provided.

Install

How do I install the Japan Tariff MCP server?

Japan Tariff runs locally as an npm package, launched with npx -y @pipeworx/mcp-japan-tariff. 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-japan-tariff

# add to Claude Code
claude mcp add pipeworx-io-japan-tariff -- npx -y @pipeworx/mcp-japan-tariff
Common questions

What is the Japan Tariff MCP server?

Japan Tariff is an MCP server listed in the public MCP registry as io.github.pipeworx-io/japan-tariff. Japan Tariff, Japan's customs tariff schedule (実行関税率表) by HS code. This page covers its npm package (@pipeworx/mcp-japan-tariff).

Is the Japan Tariff MCP server safe to use?

Japan Tariff scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Japan Tariff MCP server expose?

Japan Tariff exposes 2 tools: jp_tariff_lookup, jp_tariff_search. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.

Is the Japan Tariff MCP server still maintained?

Japan Tariff is still listed as active in the MCP registry. We last reached this channel on 21 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 Japan Tariff MCP server under?

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

What did VerifyMCP test on the Japan Tariff MCP server?

VerifyMCP ran 15 checks on Japan Tariff, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Japan Tariff: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.