Skip to main content
Glama
daleweaver1981

tariffmonitor-mcp

by daleweaver1981
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

tariffmonitor-mcp

MCP server for the Tariff Exposure Monitor — a live US import tariff calculator covering 19,856 HTS codes.

Give Claude (or any MCP-compatible AI) the ability to look up real stacked tariff rates and project the November 10, 2026 cliff impact on any product.

What it does

Two tools:

Tool

What it does

lookup_hts_code

Search 19,856 HTS codes by description or numeric prefix

calculate_tariff

Returns stacked rate (base + Section 301 + IEEPA + reciprocal) + Nov 10 cliff projection. Optional: annual import volume → dollar impact

Example exchange:

You: What's the tariff on athletic footwear from China, and how does the cliff change my costs if I import $800k/year?

Claude: [uses calculate_tariff with hts_code="6404.11", origin_country="CN", annual_import_value_usd=800000]
HTS 6404110000 — Footwear with outer soles of rubber/plastics...
Rate stack:
  Base rate (MFN): +20.00%
  Section 301 (List 4A): +7.50%
  IEEPA emergency tariff: +145.00%
Total current rate: 172.50%
Nov 10, 2026 cliff: 195.00% (+22.50pp jump)

Dollar impact at $800,000/yr import value:
  Current annual duties: $1,380,000
  Additional after Nov 10 cliff: $180,000/yr

Related MCP server: freight-pulse

Install (Claude Desktop)

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "tariffmonitor": {
      "command": "npx",
      "args": ["-y", "tariffmonitor-mcp"]
    }
  }
}

Restart Claude Desktop. The lookup_hts_code and calculate_tariff tools appear automatically.

Install (Cursor / other MCP clients)

{
  "mcp": {
    "servers": {
      "tariffmonitor": {
        "command": "npx",
        "args": ["-y", "tariffmonitor-mcp"]
      }
    }
  }
}

No API key required

The tool calls the free public API at adcreator-ai.com. No signup, no rate limits for reasonable use.

Related

Affiliate program

Earn 35% on every sale. Sign up here.

Built by Dale Weaver / 0xpi.

Available Tools

2 tools
calculate_tariffA

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, IEEPA, reciprocal), total current rate, and the projected rate after the November 10, 2026 cliff. Optionally computes dollar impact from annual import volume.

ParametersJSON Schema
NameRequiredDescriptionDefault
hts_codeYesHTS code — at least 6 digits, up to 10 (e.g. "6404.11" or "6404110000"). Dots and spaces are ignored.
origin_countryNoISO-2 origin country code (e.g. "CN" for China, "VN" for Vietnam, "MX" for Mexico). Default: CN.CN
annual_import_value_usdNoOptional. 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.

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Given no annotations, the description details the multi-layer tariff computation, projected rates after a specific date, and optional dollar impact. It does not cover error handling or auth, but the computational behavior is well described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured paragraph that front-loads the core purpose and then lists outputs and parameter details. Every sentence provides value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains the return structure thoroughly even without an output schema. Minor omission: no mention of error conditions or validity checks for HTS codes, but overall sufficient for a calculation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. The description adds meaningful context: HTS code format flexibility (dots ignored), default country, and the effect of the optional import value parameter on response. This exceeds the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool calculates 'full stacked US import tariff rate' for a given HTS code and origin country. It lists the return components and optional dollar impact, clearly distinguishing it from the sibling lookup_hts_code.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for tariff rate calculation but provides no explicit guidance on when to prefer it over lookup_hts_code or what prerequisites exist. The agent must infer usage from the description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

lookup_hts_codeA

Search for HTS (Harmonized Tariff Schedule) codes by description or numeric prefix. Returns up to 12 matching codes with descriptions. Use this before calculate_tariff when you only have a product description.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesProduct description (e.g. "athletic footwear") or HTS code prefix (e.g. "6404"). Min 2 characters.

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses output limit (up to 12 results) and the prerequisite relationship. Could mention auth or rate limits but minimal for a search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, then usage guideline. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple search tool: explains input, output, behavior, and when to use relative to sibling. No output schema needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the tool description adds no new information beyond what the schema already provides for the query parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for HTS codes by description or numeric prefix and returns up to 12 matches. It distinguishes itself from the sibling tool calculate_tariff.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises to use this tool before calculate_tariff when only having a product description, providing clear context for when and why to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedcalculate_tariff
    • First observedlookup_hts_code
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.4/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one for searching HTS codes by description, the other for calculating tariffs for a given code and origin country. There is no ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern (lookup_hts_code, calculate_tariff), making them predictable and easy to understand.

Tool Count4/5

With only 2 tools, the set is minimal but appropriate for its focused purpose of looking up tariffs. It could benefit from a couple more tools (e.g., list countries, get tariff history), but the count is not excessive.

Completeness4/5

The core workflow of finding an HTS code and calculating the tariff rate is covered. The calculations include multiple tariff layers and projected rates. Minor gaps exist, like lacking a tool to list supported origin countries or to update tariff data, but the essentials are present.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • ShippingRates

    vinaybhosle
    A
    license
    Not graded
    quality
    D
    maintenance
    Ocean container shipping intelligence for AI agents — D\&D tariffs, freight rates, vessel schedules, port congestion, inland haulage across 6 major carriers. 24 MCP tools.
    MIT

  • freight-pulse

    Baneado98
    A
    license
    A
    quality
    C
    maintenance
    Ocean and multimodal freight intelligence suite providing cross-validated rates, total landed cost, transit reliability, customs, risk, emissions, and unified ship decisions through 47 tools.
    47
    27
    MIT

  • Jikgu Customs MCP

    elinysh
    F
    license
    Not graded
    quality
    C
    maintenance
    Calculates estimated import duties, taxes, and customs clearance rules for overseas purchases, with all tools being read-only and operating without external API calls.
    -

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/daleweaver1981/tariffmonitor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server