accueil / serveurs / Dev & Code / io.github.f-tiger/us-import-duty-facts
io.github.f-tiger/us-import-duty-facts
serveur MCP (Model Context Protocol) · sourceradar 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.f-tiger/us-import-duty-facts est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.f-tiger/us-import-duty-facts » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 8 outils
- check_import_claim≈ 150 tokens
Fact-check a circulating claim about US import duties against the dated official record. Returns a verdict, why, and the sources. Covers the four figures still repeated everywhere in 2026: the $800 de minimis exemption, the $80–$200 postal flat duty, the ~54%/$100 courier rule, and 'reciprocal' baseline tariffs. Use this when a user quotes a number for US imports.
Paramètres, retour & exemple (1)
Paramètresclaim· string · requis
The claim in the user's words, e.g. 'under $800 is duty free'
Exemple d'appel{"name": "check_import_claim", "arguments": {"claim": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - classification_rulings≈ 225 tokens
Search CBP's own binding classification rulings (CROSS) for a product in plain words and get what CBP actually decided: ruling number, date, subject, the HTS codes it assigned — including any chapter 99 heading, which is what carries a Section 301 addition — and whether the ruling has been revoked or modified. This is precedent from the agency that decides, not a guess: it is how you check whether the code your supplier gave you matches what CBP has ruled on comparable goods. Queried live at call time from rulings.cbp.gov; nothing is mirrored here.
Paramètres, retour & exemple (2)
Paramètreslimit· number · optionnel
How many rulings to return, 1–10 (default 5)query· string · requis
The product in ordinary words, e.g. 'LED face mask', 'plush toy', 'power bank'
Exemple d'appel{"name": "classification_rulings", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - duty_passport≈ 161 tokens
Candidate HTS headings for a consumer product category, pulled daily from the official USITC HTS REST API: the candidate line, its general rate, every rated line in the heading, and the Section 301 status to verify on USTR. These are candidates chosen by category reading, not a classification ruling — the importer of record classifies.
Paramètres, retour & exemple (2)
Paramètrespick· string · optionnel
Product slug, e.g. 'pet-fountain'; omit with query to list all slugsquery· string · optionnel
Keyword matched against slug and HTS description
Exemple d'appel{"name": "duty_passport", "arguments": {"pick": "texte", "query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - duty_stack_rules≈ 172 tokens
The current China→US import duty stack, rule by rule, each with the record that establishes it and the date it was decided or published: HTS base rate, Section 301, Section 232, the struck-down IEEPA tariffs (2026-02-20), the indefinite de minimis suspension (2026-06-24), the expired postal flat rate (2026-02-28), and the MPF/HMF fee rates. Use this before quoting any US import rule from memory — the 2025 guidance that dominates training data is superseded.
Paramètres, retour & exemple (1)
Paramètrespart· string · optionnel · all | rules | fees | superseded
Which part to return; default all
Exemple d'appel{"name": "duty_stack_rules", "arguments": {"part": "all"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - import_rule_changes≈ 238 tokens
What changed in the general US import rules, newest first, from the official Federal Register API: presidential tariff actions, CBP and DHS rules, USTR notices — each with its publication date, document number and federalregister.gov link. Use `since` to get only what is new to you, the same way you would poll a changelog. Case-specific antidumping, ITC and Foreign-Trade Zone paperwork is out of scope by design and the response says so.
Paramètres, retour & exemple (3)
Paramètreslimit· number · optionnel
Maximum documents to return (default 25)since· string · optionnel
Only documents published on or after this date (YYYY-MM-DD)matched_in· string · optionnel · title_or_abstract | full_text_only | any
title_or_abstract = the import phrase is in the headline matter (usually the ones that matter); default any
Exemple d'appel{"name": "import_rule_changes", "arguments": {"limit": 1, "since": "texte", "matched_in": "title_or_abstract"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - landed_cost≈ 325 tokens
Itemise a US landed cost from rates you supply: duties (HTS base + Section 301 + Section 232 on the customs value), MPF 0.3464% with the CBP floor disclosed, HMF 0.125% on ocean entries, plus freight and insurance. Deterministic arithmetic with the assumptions and sources attached. This tool never invents a product's duty rate: omit hts_base_rate_pct and it refuses and points you at the official schedule.
Paramètres, retour & exemple (6)
Paramètresocean_entry· boolean · optionnel
True for ocean entries, which add the Harbor Maintenance Fee; default falsegoods_value_usd· number · requis
Customs value of the goods in USDsection_232_pct· number · optionnel
Section 232 addition in percent; default 0section_301_pct· number · optionnel
USTR Section 301 addition in percent (0 / 7.5 / 25 / 50 / 100); default 0hts_base_rate_pct· number · requis
The heading's general rate of duty, in percent. Look it up at hts.usitc.gov or with duty_passport; this server will not guess it.freight_insurance_usd· number · optionnel
Freight plus insurance in USD; default 0
Exemple d'appel{"name": "landed_cost", "arguments": {"goods_value_usd": 1, "hts_base_rate_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - recall_check≈ 181 tokens
Official US product recalls (CPSC saferproducts.gov API) touching a product category in the last 365 days: date, title, hazard and the cpsc.gov URL. A keyword hit means the words appear in a recall title, not that a particular supplier or SKU is affected. Use before recommending or sourcing a category.
Paramètres, retour & exemple (3)
Paramètrespick· string · optionnel
Product slug, e.g. 'cable-powerbank'query· string · optionnel
Keyword matched against the tracked categories and recall titlesonly_hits· boolean · optionnel
Only categories with at least one recall; default true when no pick/query given
Exemple d'appel{"name": "recall_check", "arguments": {"pick": "texte", "query": "texte", "only_hits": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - section_301_ladder≈ 240 tokens
The Section 301 (China) additional-duty ladder, read straight from the official USITC HTS export of chapter 99 subchapter III: which 9903.88 / 9903.91 heading carries which addition (7.5%, 10%, 15%, 25%, 50%, 100%), which U.S. note defines its list, and — where the schedule states it — the date that heading took effect. It tells you the possible rates and where coverage is defined; it never asserts that a particular HTS8 code is on a list, because that lives in U.S. note 20/31 and the USTR annexes.
Paramètres, retour & exemple (3)
Paramètresnote· string · optionnel · 20 | 31
20 = the original Section 301 lists; 31 = the increases effective 2024-09-27heading· string · optionnel
A chapter 99 heading prefix, e.g. '9903.88.03' or '9903.91'rate_pct· number · optionnel
Only headings carrying this additional rate, e.g. 25
Exemple d'appel{"name": "section_301_ladder", "arguments": {"note": "20", "heading": "texte", "rate_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».