Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Xonta Customs RU

PYPI · XONTA-CUSTOMS-MCP · 2 COMPONENTS

Import into Russia/EAEU: invoice parsing, TN VED codes, duties, VAT, fees, car recycling fee

53 Trust /100

Last scanned (13 hours ago)

Scores higher than 52% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security49
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2019 tokens (~201/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/xonta-customs-mcp@0.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 33 packages
Packages resolved 33
Stale 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,859 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
antidumping_check ~143

Check EAEU trade defence measures (antidumping duties) by code, product and origin country. Returns matching measures with the Eurasian Economic Commission decision, the decision that sets duty rates per producer, expiry date and a link. The bundled list covers measures renewed in 2026 and is not exhaustive: absence of a match is not proof that no measure applies.

NameTypeReqDescription
code––TN VED EAEU code or prefix
origin_country––ISO alpha-2 country of origin, e.g. CN, UA, AZ
product––Product words in Russian or English, e.g. 'грузовые шины'

No output schema declared.

No examples provided.

calc_import_payments ~528

Calculate import customs payments into Russia for one goods item, in RUB. Computes: import duty by the EAEU ETT rate (ad valorem, specific per kg/pcs/pair/litre, or combined 'X%, but not less than Y EUR per unit'), antidumping duty, excise, import VAT ((customs value + duty + antidumping + excise) x 22% or 10%) and the 2026 customs clearance fee by customs value bracket. Converts currencies at Bank of Russia rates. Returns a line-by-line breakdown with sources.

NameTypeReqDescription
antidumping_rate_pctnumber–Antidumping/countervailing/special duty rate in % of customs value, if a measure applies
code––TN VED EAEU code; its ETT duty rate is used if duty_rate is not given
currencystring–Currency of customs_value: RUB, CNY, USD, EUR, etc.
customs_valuenumberyesCustoms value of the goods (usually CIF to the EAEU border) in `currency`
duty_rate––Duty rate as in the tariff, overrides the code: '10', '0', '0,6 евро за 1 кг', '15, но не менее 2,5 евро за 1 пару'
exchange_rates––RUB per 1 unit, e.g. {'CNY': 11.2, 'EUR': 92.5}. If omitted, Bank of Russia rates for `on_date` are fetched
excise_rubnumber–Excise in RUB if the goods are excisable (alcohol, tobacco, fuel, cars)
on_date––Declaration date YYYY-MM-DD for exchange rates; default today
quantity_cm3––Engine displacement in cm3
quantity_kg––Net weight in kg, needed for per-kg specific rates
quantity_l––Litres
quantity_m2––Square metres
quantity_pair––Pairs (footwear)
quantity_pcs––Pieces, for per-piece rates
recycling_fee_rubnumber–Car recycling fee (утильсбор) in RUB from calc_recycling_fee, to show the full cost of importing a vehicle. Not part of the VAT base
vat_rateinteger–Import VAT rate in 2026: 22 general, 10 for goods on Government lists (some food, children's goods, medical), 0 if exempt

No output schema declared.

No examples provided.

calc_recycling_fee ~367

Recycling fee (утилизационный сбор) for a passenger car (category M1) imported into Russia. Uses the official coefficient table (Decree 1291 as amended by Decree 1713 of 01.11.2025): base rate 20 000 RUB x coefficient by engine type, volume, power band (kW), age and year (Dec 2025, 2026 ... 2030). Covers the commercial table and the personal-use table (0.17 / 0.26 for up to 160 hp and up to 3 l). Returns the coefficient, band and source.

NameTypeReqDescription
eaeu_extra_rubnumber–For cars released in another EAEU country: sum of Ктп + Кндс + Ка (duty, VAT, excise differences), if known
enginestringyesice = petrol/diesel; hybrid_parallel counts as ICE; ev = electric; hybrid_series = series hybrid (counts as EV)
engine_volume_cc––Engine displacement in cm3 (required for ice and hybrid_parallel)
older_than_3_yearsboolean–True if more than 3 years have passed since the production date
on_date––Date YYYY-MM-DD the fee is calculated for; default today. Tables run Dec 2025 - 2030
personal_useboolean–Imported by an individual for personal use (preferential 3 400 / 5 200 RUB up to 160 hp and 3 l)
power_hp––Engine power in horsepower (л.с.); for EVs the 30-minute max power
power_kw––Engine power in kW, alternative to power_hp

No output schema declared.

No examples provided.

classification_rulings_search ~106

Search EEC (Eurasian Economic Commission) decisions on classification of specific goods. These decisions are binding for all EAEU customs and are the strongest evidence for a code. Returns the decision number and date, the product, the TN VED code or heading and a source link.

NameTypeReqDescription
code––TN VED code or heading, e.g. '9013'
query––Product words, e.g. 'прицел тепловизионный'

No output schema declared.

No examples provided.

customs_clearance_fee ~105

Customs clearance fee (сбор за таможенные операции) for an import declaration into Russia in 2026. The fee depends on the total customs value of the declaration: from 1 231 RUB (up to 200 000) to 73 860 RUB (over 10 million). Also returns the full bracket table and the legal source.

NameTypeReqDescription
total_customs_value_rubnumberyesTotal customs value of all goods in the declaration, RUB

No output schema declared.

No examples provided.

exchange_rates ~62

Official Bank of Russia exchange rates (RUB per 1 unit) used for customs payments.

NameTypeReqDescription
currencies––Currency codes, e.g. ['CNY','USD','EUR']; all if omitted
on_date––Date YYYY-MM-DD; default today

No output schema declared.

No examples provided.

parse_invoice ~224

Parse a supplier's commercial invoice or packing list into customs-ready line items. Extracts invoice number, date, parties, currency, Incoterms and country of origin, and for each line: description, model, material, supplier HS code, quantity, unit, price, amount, net and gross weight. Checks arithmetic (qty x price, sum vs total), explains what to add to the invoice value for customs value under the given Incoterms, and suggests a TN VED search query per line (HS code first 6 digits or Russian keywords). Feed the lines to tnved_search and calc_import_payments.

NameTypeReqDescription
file_url––Public link to the invoice file: .xlsx/.csv are parsed directly; PDF/scans/DOCX go through DocParse when the server has it configured
invoice_text––Invoice or packing list as Markdown or plain text, e.g. the output of DocParse. Tables with English, Chinese (品名, 数量, 单价, 金额, 净重) or Russian headers

No output schema declared.

No examples provided.

server_status ~32

Data versions of this server: tariff load date and source, antidumping and rulings list dates, fee table source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tnved_code_info ~142

Get everything known about one TN VED EAEU code. Returns the official name with parent headings, the ETT import duty rate parsed into ad valorem / specific / combined parts, EAEU antidumping measures that may apply (filtered by origin country if given) and EEC classification rulings for this heading.

NameTypeReqDescription
codestringyesTN VED EAEU code, 4-10 digits, spaces allowed, e.g. '8413 60 310 0'
origin_country––ISO 3166-1 alpha-2 country of origin, e.g. 'CN', to check antidumping measures

No output schema declared.

No examples provided.

tnved_search ~150

Search the TN VED EAEU (ТН ВЭД ЕАЭС) commodity nomenclature by product words or code prefix. Returns candidate 10-digit codes with official names and the ETT import duty rate. Use the candidates to pick a code, then call tnved_code_info for details. Text search matches nomenclature wording, so use technical terms (material, function), not brand names. Results are candidates, not a classification decision.

NameTypeReqDescription
limitinteger–Max results
querystringyesProduct description in Russian (e.g. 'насос шестеренный гидравлический') or a code prefix like '8413' or '8413603100'

No output schema declared.

No examples provided.

Install

How do I install the Xonta Customs RU MCP server?

Xonta Customs RU runs locally as a PyPI package, launched with uvx xonta-customs-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · xonta-customs-mcp

# add to Claude Code
claude mcp add ru-xonta-customs -- uvx xonta-customs-mcp
Common questions

What is the Xonta Customs RU MCP server?

Xonta Customs RU is an MCP server listed in the public MCP registry as ru.xonta/customs. Import into Russia/EAEU: invoice parsing, TN VED codes, duties, VAT, fees, car recycling fee. This page covers its PyPI package (xonta-customs-mcp).

Is the Xonta Customs RU MCP server safe to use?

Xonta Customs RU scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 Xonta Customs RU MCP server expose?

Xonta Customs RU exposes 10 tools: tnved_search, tnved_code_info, calc_import_payments, calc_recycling_fee, parse_invoice, and 5 more. Their descriptions and schemas cost roughly 1,859 tokens of context every time the server is loaded.

Is the Xonta Customs RU MCP server still maintained?

Xonta Customs RU is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Xonta Customs RU MCP server under?

Xonta Customs RU declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Xonta Customs RU MCP server?

VerifyMCP ran 14 checks on Xonta Customs RU, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Xonta Customs RU: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.