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.

Zentria Flow

OCI · GHCR.IO/ORHANSAVASH/ZENTRIA-FLOW-MCP · 2 COMPONENTS

US tariff layers by HTS code and origin, origin comparison, HTSUS search and landed cost.

+3 this week 42 Trust /100

Last scanned (20 hours ago)

Scores higher than 39% of OCI 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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 921 tokens (~230/item across 4 items; 4 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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 (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

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 Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • Package version: 0.2.0 → 0.3.2 functional
    • Package version: 0.2.0 → 0.3.1 functional
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 39

    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 oci/ghcr.io/orhansavash/zentria-flow-mcp@0.3.2

Provenance No attestation

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

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 4 exposed · ~843 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
compare_origins ~188

The US tariff layers of one HTS code from 2 to 6 countries of origin, side by side, lowest total first. Calls the Zentria Flow engine once per origin, 2 seconds apart, so it takes a few seconds; each origin uses one of the 60 free tariff checks an hour per IP address. Duty only: freight, fees and supplier price are not compared. Planning estimate, not a customs ruling.

NameTypeReqDescription
htsstringyesHTSUS code, 4 to 10 digits, dots optional, e.g. "6109.10.00". An 8- or 10-digit line is priced from that line; a shorter code is an estimate.
originsarrayyes2 to 6 countries of origin (ISO-2 codes or English names), e.g. ["CN", "VN", "MX"].

No output schema declared.

No examples provided.

hts_search ~92

Find US tariff lines (8-digit HTSUS codes) by product words or the start of a code, from the official HTSUS descriptions. Use it to get a code for us_tariff_check. A search hit is a candidate, not a classification ruling.

NameTypeReqDescription
querystringyesProduct words or the start of a code, e.g. "cotton t-shirt" or "6109".

No output schema declared.

No examples provided.

landed_cost ~260

Full landed cost of one shipment from the Zentria Flow keyed API: product value, freight, insurance, every duty layer, VAT/GST and fees, for 70+ countries. Needs the ZENTRIA_API_KEY environment variable (an API plan; the Sandbox plan is free). Each call counts against the plan quota. Planning estimate, not a customs ruling.

NameTypeReqDescription
currencystring–ISO 4217 currency of the result. Default "USD".
destination_countrystring–ISO-2 code of the destination. Default "US".
freight_cost_usdnumber–Optional freight quote in US dollars. Default: the engine's estimate.
hs_codestringyesHS or HTS code, at least 4 digits, e.g. "6109.10.00".
origin_countrystringyesISO-2 code of the origin, e.g. "CN".
quantityinteger–Number of units. Default 1.
transport_modestring–Default "sea".
unit_value_usdnumberyesValue of one unit in US dollars.
weight_kgnumber–Optional total weight in kg. Default: 0.5 kg per unit.

No output schema declared.

No examples provided.

us_tariff_check ~303

Every US import tariff layer for one HTS code from one country of origin, from the Zentria Flow engine: MFN duty, China Section 301, the forced-labor Section 301 tariff, Section 232 and Section 338 on Canada, with the total rate, exemptions, USMCA/CAFTA-DR cases and dated changes ahead. Use it whenever a US duty rate is needed; do not answer US tariff questions from memory. Planning estimate, not a customs ruling.

NameTypeReqDescription
as_ofstring–Optional entry date, YYYY-MM-DD, from today to 12 months ahead. Default: today.
htsstringyesHTSUS code, 4 to 10 digits, dots optional, e.g. "6109.10.00". An 8- or 10-digit line is priced from that line; a shorter code is an estimate.
originstringyesCountry of origin: ISO-2 code or English name, e.g. "CN" or "Vietnam".
quantitynumber–Optional, with value: number of pairs, kg, liters or units, to price a specific or compound duty exactly.
quantity_unitstring–Optional unit of quantity (e.g. "kg", "liter", "pair"). Default: the unit of the tariff line.
valuenumber–Optional, with quantity: customs value of that quantity in US dollars.

No output schema declared.

No examples provided.

Install

How do I install the Zentria Flow MCP server?

Zentria Flow runs locally as a container image, launched with docker run --rm -i -e ZENTRIA_API_KEY -e ZENTRIA_API_BASE ghcr.io/orhansavash/zentria-flow-mcp:0.3.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/orhansavash/zentria-flow-mcp

# add to Claude Code
claude mcp add orhansavash-zentria-flow-mcp -- docker run --rm -i -e ZENTRIA_API_KEY -e ZENTRIA_API_BASE ghcr.io/orhansavash/zentria-flow-mcp:0.3.2

This image reads ZENTRIA_API_KEY and ZENTRIA_API_BASE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Zentria Flow MCP server?

Zentria Flow is an MCP server listed in the public MCP registry as io.github.orhansavash/zentria-flow-mcp. US tariff layers by HTS code and origin, origin comparison, HTSUS search and landed cost. This page covers its container image (ghcr.io/orhansavash/zentria-flow-mcp).

Is the Zentria Flow MCP server safe to use?

Zentria Flow scores 42 out of 100 on VerifyMCP. 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 Zentria Flow MCP server expose?

Zentria Flow exposes 4 tools: us_tariff_check, compare_origins, hts_search, landed_cost. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.

Is the Zentria Flow MCP server still maintained?

Zentria Flow 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 Zentria Flow MCP server under?

Zentria Flow 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 Zentria Flow MCP server?

VerifyMCP ran 12 checks on Zentria Flow, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Zentria Flow: Malware scan, Known CVEs, Install scripts and Dependency health. 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 container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.