Skip to content

Tariff Monitor: US Import Duty & HTS Lookup MCP server

io.github.daleweaver1981/tariffmonitor-mcpdaleweaver1981streamable-httpv1.6.6Scanned

US import tariffs: classify to HTS code, stacked rate (MFN+301+232+forced-labor), compare origins.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Tariff Monitor: US Import Duty & HTS Lookup MCP server can do

The Tariff Monitor: US Import Duty & HTS Lookup MCP server is published by the GitHub account daleweaver1981. It has 4 tools. It can create or change data (2 tools: calculate_tariff and classify_product), but cannot delete data. 2 tools only read.

4 tools bring in text other people can write (lookup_hts_code, calculate_tariff, classify_product and 1 more).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.6.6.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • calculate_tariffCalculate the full stacked US import tariff rate for an HTS code from a specific origin country.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,278 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...nd are not included. Optionally computes dollar impact from annual import volume."

      What this check looks for
    Description, as the server wrote it
    Calculate the full stacked US import tariff rate for an HTS code from a specific origin country. Returns: base rate, each additional layer (China Section 301 matched by HTS line to Lists 1, 2, 3, 4A and the 2024 four-year-review increases; Section 232 steel, aluminum and copper matched by HTS line to the U.S. note 16 lists, headings 9903.82.02-.26: 50% on listed metal articles, 25% on listed derivatives, UK and 15%-floor rates, with the metal-content conditions stated; other Section 232 programs (vehicles and parts, wood products, trucks, semiconductors, drones) flagged as needs review when the line is named, not computed; Section 301 Brazil, 25% since 22 Jul 2026, heading 9903.05.01, with its exemption lists; and the 2026 Section 301 forced-labor tariff on 60 economies: 10% or 12.5% by origin, or a 10%/12.5% cap net of MFN for the EU, Taiwan, Japan, South Korea and Switzerland, in effect since 24 Jul 2026, FR Doc. 2026-15181, HTS 9903.05.20-9903.05.84), the total current rate, the date the data was checked, and notes naming each exemption or assumption (Section 232 goods, USMCA- or CAFTA-DR-qualifying entries, listed products). For products of Canada it notes that Section 338 duties may apply; their product lists are published only as images, so they are not computed. Also states when the Section 301 China product exclusions end: through 11:59 p.m. ET on January 9, 2027 (Federal Register, FR Doc. 2026-22925, which extended the earlier 9 Nov 2026 end). Rates are effective-date aware: pass date (YYYY-MM-DD) for the rule in force on that entry date. For products of China it applies the 178 Section 301 product exclusions by statistical number (U.S. note 20(vvv)/(www)) through their end date, and the maritime Section 301 headings (9903.92.10 +25% on ship-to-shore cranes; from 10 Jan 2027 (the maritime action is suspended through 9 Jan 2027 by FR Doc. 2026-22867) 9903.91.14 +100% on those cranes and 9903.91.12 +100% on intermodal chassis, shown as "up to" because chapter 99 does not say how it combines with List 3), each with its legal source, and says when a rate depends on a proposed, not final, extension. Figures are estimates; IEEPA tariffs ended 20 Feb 2026 and are not included. Optionally computes dollar impact from annual import volume.

    Annotations the server declares

    • title: Calculate US import tariff
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • classify_productSuggest up to 3 US HTS-10 codes for a product from a product description or an invoice line.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Suggest up to 3 US HTS-10 codes for a product from a product description or an invoice line. Each candidate has: the HTS description from our own HTS data (never written by a model), a one-line reason that quotes that description, a confidence label (high, medium or low), and, when you pass origin_country, the stacked duty from the same logic as calculate_tariff (MFN + Section 301 + Section 232 + the 2026 forced-labor layer). How it works: candidates are retrieved only from our HTS data; a self-hosted model on our own server (no outside AI provider) ranks only among those candidates, and any code that is not in our data is dropped. These are SUGGESTIONS TO VERIFY, not a classification ruling: binding rulings come from US Customs and Border Protection (CBP, https://rulings.cbp.gov/), and the right line often depends on material, construction and use details a one-line description may not show. Measured on our server: about 1 to 3 minutes per call because the model runs on shared CPU hardware (set a long client timeout); if the model server is busy or unreachable the tool returns a retryable error. Free public endpoint: each call counts as 1 of your 25 daily calls. Running the npm package locally needs your own Ollama server (set TM_OLLAMA_URL).

    Annotations the server declares

    • title: Classify a product to HTS codes (description or invoice line)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • compare_originsCompare the estimated US import tariff for ONE HTS code across several origin countries side by side (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "compare_origins" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Compare the estimated US import tariff for ONE HTS code across several origin countries side by side (e.g. China vs Vietnam vs Mexico vs India), for sourcing and "China plus one" decisions. For each origin returns the total current rate, the layers that make it up (MFN base, Section 301 China, Section 232 by HTS line, Section 301 Brazil, 2026 Section 301 forced-labor tariff) and the rate after the Section 301 China exclusions end (through 11:59 p.m. ET on 9 Jan 2027 per the Federal Register, FR Doc. 2026-22925), sorted lowest first, with the dollar duty when an annual import value is given. Estimates only; preferential rates (USMCA, FTAs) depend on rules of origin and are not assumed.

    Annotations the server declares

    • title: Compare tariffs by origin country
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • lookup_hts_codeFind the US HTS (Harmonized Tariff Schedule) code for a product, by plain-language product name or numeric prefix, from the official USITC schedule (19,856 10-digit codes).Reads text others writeNo findings

    Why it is in this group

    • The name "lookup_hts_code" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Find the US HTS (Harmonized Tariff Schedule) code for a product, by plain-language product name or numeric prefix, from the official USITC schedule (19,856 10-digit codes). Use this first whenever you have a product name rather than a code (e.g. "laptop", "t-shirt", "water bottle", "wireless earbuds", "toys", "e-bike", "running shoes"), then pass a code to calculate_tariff or compare_origins. Everyday shopping words that a plain search of the schedule misses are mapped to the official heading that covers them (e.g. laptop -> 8471.30 "Portable automatic data processing machines"), and the answer names that heading; when a word commonly falls under more than one heading (water bottle: 7323.93 stainless, 9617.00 vacuum flasks, 3924.10 plastic) each is listed, with the 10-digit lines ranked by match to the query. Otherwise descriptions are matched as one phrase; if a phrase matches nothing the tool retries single words and says which word it used. Returns up to 12 codes.

    Annotations the server declares

    • title: Look up HTS code
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:23 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://adcreator-ai.com/mcp-free: tools/list returned 4 tools to an anonymous client, including calculate_tariff (write), classify_product (write)

    What this check looks for

Posture changes

  1. Nov 10, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,278 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...nd are not included. Optionally computes dollar impact from annual import volume."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2
  2. Tools2 changed.~2 changedView diff
  3. Tools1 added, 2 changed.+1 added~2 changedView diff
  4. Tools3 changed.~3 changedView diff
  5. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.6.6. Values in angle brackets are yours to fill in.

claude mcp add --transport http tariffmonitor https://adcreator-ai.com/mcp-free
claude mcp add --transport http tariffmonitor https://adcreator-ai.com/mcp-free

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tariffmonitor__lookup_hts_code",
      "mcp__tariffmonitor__compare_origins"
    ],
    "ask": [
      "mcp__tariffmonitor__calculate_tariff",
      "mcp__tariffmonitor__classify_product"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tariffmonitor. Review it before you use it.

Capability tags behind 4 rules
  • mcp__tariffmonitor__lookup_hts_code untrusted-input
  • mcp__tariffmonitor__calculate_tariff untrusted-input
  • mcp__tariffmonitor__classify_product untrusted-input
  • mcp__tariffmonitor__compare_origins untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.daleweaver1981/tariffmonitor-mcp/verify?hash=7d160860ad01b210d86e127438bf6a45396af8624f6c050fbb1f6c54c5356d74" | jq -e '.changed == false'

Pinned hash 7d160860ad01, from Nov 14, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.daleweaver1981/tariffmonitor-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.daleweaver1981/tariffmonitor-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.daleweaver1981/tariffmonitor-mcp.svg)](https://radar.anlyon.com/servers/io.github.daleweaver1981/tariffmonitor-mcp)

Source: MCP Registry · repository. Synced Nov 14, 2026, 01:17 UTC.

Tariff Monitor: US Import Duty & HTS Lookup MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Tariff Monitor: US Import Duty & HTS Lookup MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Tariff Monitor: US Import Duty & HTS Lookup MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Tariff Monitor: US Import Duty & HTS Lookup MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Tariff Monitor: US Import Duty & HTS Lookup MCP server have?

4 tools: 2 write, 2 read. calculate_tariff, classify_product, lookup_hts_code and compare_origins.

Does the Tariff Monitor: US Import Duty & HTS Lookup MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Tariff Monitor: US Import Duty & HTS Lookup MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Tariff Monitor: US Import Duty & HTS Lookup MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.