htsapi.dev MCP server
Related Servers
Alternatives to htsapi.dev MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to look up US import tariff layers for an HTS code and origin, compare origins side by side, search HTSUS lines by keyword or partial code, and calculate full landed costs for 70+ countries. Every answer is date-stamped and tied to a named HTSUS revision, and three of the four tools work without an account or API key.4MIT
- AlicenseNot gradedqualityCmaintenanceProvides access to US import tariff rates via the USITC Harmonized Tariff Schedule, enabling natural language queries for tariff data.82 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables searching U.S. Harmonized Tariff Schedule commodity descriptions and code prefixes, inspecting classification headings and ancestry, browsing chapters, and retrieving published duty-rate columns and partial Chapter 99 evidence via MCP.86 npm1Apache 2.0
- AlicenseBqualityBmaintenanceTurns your AI assistant into a US import duty research tool, enabling HTS code lookup, landed-cost calculation, and tariff change tracking using official USITC data.5342 npm3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to parse supplier invoices, look up EAEU TN VED codes, check antidumping measures and classification rulings, and calculate Russian import duties, VAT, customs fees, and vehicle recycling fees using sourced rates.10MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search Chinese HS commodity codes, retrieve detailed tariff and regulatory information, and calculate import taxes using 2026 import/export tariff data.MIT
TDQS
Scored across 8 tools
The two retrieval entry points are clearly distinguished (search_rulings by product meaning vs rulings_under_code by code), and get_ruling is a distinct single-record fetch. classify_product, lookup_hts_code and importers_paid are explicitly contrasted in their descriptions. The only soft overlap is get_notes vs heading_scope, which both surface legal notes applied to a heading/code, though one is statutory text and the other ruling-quoted explanatory passages.
All names use snake_case, which is consistent throughout. Most follow verb_noun (search_rulings, get_ruling, classify_product, lookup_hts_code, get_notes), with a few noun-phrase exceptions (importers_paid, heading_scope, rulings_under_code) that are still readable and self-descriptive.
Eight tools is well within the ideal range and each maps to a distinct step in the classification workflow: search, retrieve, classify, browse the schedule, read notes, read explanatory scope, check historical rulings, check duty paid. No tool appears redundant or filler.
The surface covers the full classification research loop from product description to code lookup to legal authority to real-world duty evidence. Minor gaps: there is no forward duty calculator or special-program/TRQ eligibility check, and AD/CVD is explicitly out of scope and has no tool, but agents can work around these via importers_paid and lookup_hts_code.