# Zentria Flow (oci · ghcr.io/orhansavash/zentria-flow-mcp)

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

- Trust score: 42/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `zentriaflow.com`: 72/100, [markdown](https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/zentriaflow.md), [page](https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/zentriaflow)
- oci · `ghcr.io/orhansavash/zentria-flow-mcp`: 42/100 (this document), [markdown](https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/ghcr-io-orhansavash-zentria-flow-mcp.md), [page](https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/ghcr-io-orhansavash-zentria-flow-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/orhansavash/zentria-flow-mcp`
- Version: `0.3.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - 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 could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
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.

### Cursor

```json
{
  "mcpServers": {
    "orhansavash-zentria-flow-mcp": {
      "command": "docker",
      "args": [
        "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.

### VS Code

```json
{
  "servers": {
    "orhansavash-zentria-flow-mcp": {
      "command": "docker",
      "args": [
        "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.

### Codex

```bash
codex 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "orhansavash-zentria-flow-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "ZENTRIA_API_KEY",
        "-e",
        "ZENTRIA_API_BASE",
        "ghcr.io/orhansavash/zentria-flow-mcp:0.3.2"
      ],
      "enabled": true
    }
  }
}
```

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.

### Hermes

```yaml
mcp_servers:
  orhansavash-zentria-flow-mcp:
    command: "docker"
    args: ["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.

### Netclaw

```json
{
  "McpServers": {
    "orhansavash-zentria-flow-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "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.

### Other

```json
{
  "mcpServers": {
    "orhansavash-zentria-flow-mcp": {
      "command": "docker",
      "args": [
        "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 42, +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.

### 2026-11-19 (score 41, 0)

- [functional] Package version: 0.2.0 → 0.3.2
- [functional] Package version: 0.2.0 → 0.3.1

### 2026-11-18 (score 41, +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.

### 2026-11-16 (score 40, +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.

### 2026-11-14 (score 39)

First indexed and scored.

## MCP tools (4)

### `us_tariff_check` (~303 tokens)

US tariff check

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.

Input parameters:

- `as_of` (string): Optional entry date, YYYY-MM-DD, from today to 12 months ahead. Default: today.
- `hts` (string, required): HTSUS 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.
- `origin` (string, required): Country of origin: ISO-2 code or English name, e.g. "CN" or "Vietnam".
- `quantity` (number): Optional, with value: number of pairs, kg, liters or units, to price a specific or compound duty exactly.
- `quantity_unit` (string): Optional unit of quantity (e.g. "kg", "liter", "pair"). Default: the unit of the tariff line.
- `value` (number): Optional, with quantity: customs value of that quantity in US dollars.

### `compare_origins` (~188 tokens)

Compare US tariffs by origin

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.

Input parameters:

- `hts` (string, required): HTSUS 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.
- `origins` (array, required): 2 to 6 countries of origin (ISO-2 codes or English names), e.g. ["CN", "VN", "MX"].

### `hts_search` (~92 tokens)

Search HTSUS lines

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.

Input parameters:

- `query` (string, required): Product words or the start of a code, e.g. "cotton t-shirt" or "6109".

### `landed_cost` (~260 tokens)

Landed cost of a shipment

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.

Input parameters:

- `currency` (string): ISO 4217 currency of the result. Default "USD".
- `destination_country` (string): ISO-2 code of the destination. Default "US".
- `freight_cost_usd` (number): Optional freight quote in US dollars. Default: the engine's estimate.
- `hs_code` (string, required): HS or HTS code, at least 4 digits, e.g. "6109.10.00".
- `origin_country` (string, required): ISO-2 code of the origin, e.g. "CN".
- `quantity` (integer): Number of units. Default 1.
- `transport_mode` (string): Default "sea".
- `unit_value_usd` (number, required): Value of one unit in US dollars.
- `weight_kg` (number): Optional total weight in kg. Default: 0.5 kg per unit.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/ghcr-io-orhansavash-zentria-flow-mcp#diagnostics

## Score history

- 2026-11-21: 42
- 2026-11-20: 42
- 2026-11-19: 41
- 2026-11-18: 41
- 2026-11-17: 40
- 2026-11-16: 40
- 2026-11-15: 39
- 2026-11-14: 39

## 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.

## Links

- GitHub Container Registry: https://ghcr.io/orhansavash/zentria-flow-mcp
- Repository: https://github.com/orhansavash/zentria-flow-mcp
- Website: https://zentriaflow.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/ghcr-io-orhansavash-zentria-flow-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/ghcr-io-orhansavash-zentria-flow-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/ghcr-io-orhansavash-zentria-flow-mcp.json
- HTML version of this page: https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/ghcr-io-orhansavash-zentria-flow-mcp
