# io.github.opsloft/tariff-resolver (npm · tariff-resolver)

US import duty research: HTS codes, Chapter 99 duties, MPF/HMF fees, landed cost. USITC data.

- Trust score: 83/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- npm · `tariff-resolver`: 83/100 (this document), [markdown](https://verifymcp.io/servers/opsloft-tariff-resolver/tariff-resolver.md), [page](https://verifymcp.io/servers/opsloft-tariff-resolver/tariff-resolver)

## Channel facts

- Registry: `npm`
- Package: `tariff-resolver`
- Version: `1.1.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-09-22.

- **Supply Chain Security**: 98/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.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 625 tokens (~125/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 5 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.

## Install

### How do I install the io.github.opsloft/tariff-resolver MCP server?

io.github.opsloft/tariff-resolver runs locally as an npm package, launched with npx -y tariff-resolver. 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 opsloft-tariff-resolver -- npx -y tariff-resolver
```

### Cursor

```json
{
  "mcpServers": {
    "opsloft-tariff-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "tariff-resolver"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "opsloft-tariff-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "tariff-resolver"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add opsloft-tariff-resolver -- npx -y tariff-resolver
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "opsloft-tariff-resolver": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tariff-resolver"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add opsloft-tariff-resolver --command npx --arg -y --arg tariff-resolver
```

### Hermes

```yaml
mcp_servers:
  opsloft-tariff-resolver:
    command: "npx"
    args: ["-y", "tariff-resolver"]
```

### Netclaw

```json
{
  "McpServers": {
    "opsloft-tariff-resolver": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tariff-resolver"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add opsloft-tariff-resolver -t stdio -c npx -a -y tariff-resolver
```

### Other

```json
{
  "mcpServers": {
    "opsloft-tariff-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "tariff-resolver"
      ]
    }
  }
}
```

## 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-09-21 (score 83, −1)

- [functional] Stability: pass → 0.90

### 2026-09-19 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 83, +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.

### 2026-09-14 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `search_hs_candidates` (~181 tokens)

Search HTS code candidates

Returns top 8-10 digit HTS code candidates (with MFN/FTA rates and CBP CROSS ruling links) for a product description. Results are CANDIDATES for pre-broker screening, not a classification ruling. IMPORTANT: the HTS uses legal terminology, not trade names — BEFORE CALLING, rewrite the product description into HTS-style material + use nouns (e.g. 'pink kids backpack' → 'travel bags of man-made fibers'; 'water bottle' → 'vacuum flask' or 'bottle of plastics'). If you get 0 results, retry with 2-3 different phrasings.

Input parameters:

- `limit` (integer): Number of candidates
- `product_description` (string, required): Product description in English: material, use, composition (e.g. 'stainless steel insulated water bottle 500ml')

### `calculate_tariff_scenario` (~246 tokens)

Calculate tariff scenario

Returns the HTS code's MFN/FTA base rate, ALL active chapter 99 rules (IEEPA/301/232 additional duties) matching the origin as verbatim text, and MPF/HMF fees. The LLM should walk the chapter-99 exception chains itself to stack the right duty layers, explain each step to the user, and always note this is an estimate.

Input parameters:

- `customs_value_usd` (number, required): Customs value of the shipment (USD)
- `hts_code` (string, required): 8-10 digit HTS code, with or without dots
- `ocean_freight` (boolean): Ocean shipment? (applies HMF)
- `origin_country` (string, required): Country of origin: ISO-3166 alpha-2 code (e.g. 'CN') or English country name (e.g. 'China')
- `quantity` (number): Quantity in the code's units (No./Dz Pcs...) — needed for per-piece specific duties
- `weight_kg` (number): Total weight (kg) — REQUIRED when the code carries a specific duty per kg (e.g. '12.4¢/kg')

### `watch_tariff_changes` (~98 tokens)

Watch HTS codes for tariff changes

Saves HTS codes (with optional origin) to a local watchlist. After each dataset refresh, call check_tariff_updates to see whether the rates on these codes changed. This is how you track 2025-2026 tariff volatility without manual re-checking.

Input parameters:

- `hts_codes` (array, required): 8-10 digit HTS codes to watch
- `origin_country` (string): Shared origin for the shipment (optional)

### `check_tariff_updates` (~76 tokens)

Check tariff changes between revisions

Compares the current HTS snapshot with the previously fetched one. Call without codes to check the whole watchlist. Returns each change: code, column (general/special/other/additionalDuties), old → new value.

Input parameters:

- `hts_codes` (array): Limit to these codes (default: the watchlist)

### `dataset_info` (~24 tokens)

Dataset info

Fetch date, source, license, row counts — use to check data freshness.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/opsloft-tariff-resolver/tariff-resolver#diagnostics

## Score history

- 2026-09-22: 83
- 2026-09-21: 83
- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 82
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 80
- 2026-09-08: 79
- 2026-09-07: 79
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 76
- 2026-09-01: 76
- 2026-08-31: 76
- 2026-08-30: 75
- 2026-08-29: 75
- 2026-08-28: 74
- 2026-08-27: 74
- 2026-08-26: 73
- 2026-08-25: 72
- 2026-08-24: 71

## Common questions

### What is the io.github.opsloft/tariff-resolver MCP server?

io.github.opsloft/tariff-resolver is an MCP server listed in the public MCP registry as io.github.opsloft/tariff-resolver. US import duty research: HTS codes, Chapter 99 duties, MPF/HMF fees, landed cost. USITC data. This page covers its npm package (tariff-resolver).

### Is the io.github.opsloft/tariff-resolver MCP server safe to use?

io.github.opsloft/tariff-resolver scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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.opsloft/tariff-resolver MCP server expose?

io.github.opsloft/tariff-resolver exposes 5 tools: search_hs_candidates, calculate_tariff_scenario, watch_tariff_changes, check_tariff_updates, dataset_info. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.

### Is the io.github.opsloft/tariff-resolver MCP server still maintained?

io.github.opsloft/tariff-resolver is still listed as active in the MCP registry. We last reached this channel on 22 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.opsloft/tariff-resolver MCP server under?

io.github.opsloft/tariff-resolver 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/tariff-resolver
- Socket report: https://socket.dev/npm/package/tariff-resolver
- Repository: https://github.com/opsloft/tariff-resolver
- Website: https://opsloft.dev/
- Changelog RSS feed: https://verifymcp.io/servers/opsloft-tariff-resolver/tariff-resolver.xml
- Changelog JSON feed: https://verifymcp.io/servers/opsloft-tariff-resolver/tariff-resolver.json
- HTML version of this page: https://verifymcp.io/servers/opsloft-tariff-resolver/tariff-resolver