io.github.daleweaver1981/tariffmonitor-mcp
NPM · TARIFFMONITOR-MCP · SCANNED SEP 20
US import tariff estimates: HTS lookup and stacked rate (MFN + Section 301 + 232). No API key.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 409 tokens (~204/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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 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
How do I install the io.github.daleweaver1981/tariffmonitor-mcp server?
io.github.daleweaver1981/tariffmonitor-mcp runs locally as an npm package, launched with npx -y tariffmonitor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tariffmonitor-mcp
claude mcp add daleweaver1981-tariffmonitor-mcp -- npx -y tariffmonitor-mcp
{
"mcpServers": {
"daleweaver1981-tariffmonitor-mcp": {
"command": "npx",
"args": [
"-y",
"tariffmonitor-mcp"
]
}
}
} {
"servers": {
"daleweaver1981-tariffmonitor-mcp": {
"command": "npx",
"args": [
"-y",
"tariffmonitor-mcp"
]
}
}
} codex mcp add daleweaver1981-tariffmonitor-mcp -- npx -y tariffmonitor-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"daleweaver1981-tariffmonitor-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tariffmonitor-mcp"
],
"enabled": true
}
}
} openclaw mcp add daleweaver1981-tariffmonitor-mcp --command npx --arg -y --arg tariffmonitor-mcp
mcp_servers:
daleweaver1981-tariffmonitor-mcp:
command: "npx"
args: ["-y", "tariffmonitor-mcp"] {
"McpServers": {
"daleweaver1981-tariffmonitor-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tariffmonitor-mcp"
]
}
}
} assistant mcp add daleweaver1981-tariffmonitor-mcp -t stdio -c npx -a -y tariffmonitor-mcp
{
"mcpServers": {
"daleweaver1981-tariffmonitor-mcp": {
"command": "npx",
"args": [
"-y",
"tariffmonitor-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −1
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Package version: 1.0.0 → 1.2.1 functional
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 +5
- Source repository: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 15 Sept 26 −4
- Provenance: pass → unverified ▼ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/tariffmonitor-mcp@1.2.1
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
calculate_tariff ~273
Calculate the full stacked US import tariff rate for an HTS code from a specific origin country. Returns: base rate, each additional layer (Section 301, Section 232), total current rate, and the projected rate after the November 10, 2026 Section 301 exclusion expiry. Figures are estimates; IEEPA tariffs ended 20 Feb 2026 and are not included. Optionally computes dollar impact from annual import volume.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_import_value_usd | number | – | Optional. Your annual import value in USD. If provided, the response includes the dollar cost of current duties and the additional cost from the Nov 10 cliff. |
| hts_code | string | yes | HTS code — at least 6 digits, up to 10 (e.g. "6404.11" or "6404112030"). Dots and spaces are ignored. Zero-padded headings such as "6404110000" are not real schedule codes; if the exact code is not f… |
| origin_country | string | – | ISO-2 origin country code (e.g. "CN" for China, "VN" for Vietnam, "MX" for Mexico). Default: CN. |
No output schema declared.
No examples provided.
lookup_hts_code ~136
Search for HTS (Harmonized Tariff Schedule) codes by description or numeric prefix. Returns up to 12 matching codes. Use this before calculate_tariff when you only have a product description. Descriptions are matched as a single phrase, so one keyword ("footwear") matches far more than a phrase ("athletic footwear"); if a phrase matches nothing this tool retries the individual words and tells you which word it used.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Product keyword (e.g. "footwear") or HTS code prefix (e.g. "6404"). Minimum 2 characters. Single keywords match best. |
No output schema declared.
No examples provided.
What is the io.github.daleweaver1981/tariffmonitor-mcp server?
io.github.daleweaver1981/tariffmonitor-mcp is listed in the public MCP registry as io.github.daleweaver1981/tariffmonitor-mcp. US import tariff estimates: HTS lookup and stacked rate (MFN + Section 301 + 232). No API key. This page covers its npm package (tariffmonitor-mcp).
Is the io.github.daleweaver1981/tariffmonitor-mcp server safe to use?
io.github.daleweaver1981/tariffmonitor-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.daleweaver1981/tariffmonitor-mcp server expose?
io.github.daleweaver1981/tariffmonitor-mcp exposes 2 tools: lookup_hts_code, calculate_tariff. Their descriptions and schemas cost roughly 409 tokens of context every time the server is loaded.
Is the io.github.daleweaver1981/tariffmonitor-mcp server still maintained?
io.github.daleweaver1981/tariffmonitor-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.daleweaver1981/tariffmonitor-mcp server under?
io.github.daleweaver1981/tariffmonitor-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.