# Zentria Flow (remote · zentriaflow.com)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `zentriaflow.com`: 72/100 (this document), [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, [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

- Endpoint: `https://zentriaflow.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 655 tokens (~218/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Zentria Flow MCP server?

Zentria Flow is a hosted endpoint at https://zentriaflow.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http orhansavash-zentria-flow-mcp 'https://zentriaflow.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "orhansavash-zentria-flow-mcp": {
      "url": "https://zentriaflow.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "orhansavash-zentria-flow-mcp": {
      "type": "http",
      "url": "https://zentriaflow.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.orhansavash-zentria-flow-mcp]
url = "https://zentriaflow.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "orhansavash-zentria-flow-mcp": {
      "type": "remote",
      "url": "https://zentriaflow.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add orhansavash-zentria-flow-mcp --url 'https://zentriaflow.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  orhansavash-zentria-flow-mcp:
    url: "https://zentriaflow.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "orhansavash-zentria-flow-mcp": {
      "Transport": "http",
      "Url": "https://zentriaflow.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add orhansavash-zentria-flow-mcp -t streamable-http -u 'https://zentriaflow.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "orhansavash-zentria-flow-mcp": {
      "type": "http",
      "url": "https://zentriaflow.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-21 (score 72, +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-20 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-19 (score 71)

First indexed and scored.

## MCP tools (3)

### `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` (~148 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. 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".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/zentriaflow#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71

## 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 hosted endpoint (https://zentriaflow.com/mcp).

### Is the Zentria Flow MCP server safe to use?

Zentria Flow scores 72 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 3 tools: us_tariff_check, compare_origins, hts_search. Their descriptions and schemas cost roughly 543 tokens of context every time the server is loaded.

### Does the Zentria Flow MCP server require authentication?

No. We connected to Zentria Flow without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 did VerifyMCP test on the Zentria Flow MCP server?

VerifyMCP ran 13 checks on Zentria Flow, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://zentriaflow.com/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/zentriaflow.xml
- Changelog JSON feed: https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/zentriaflow/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/zentriaflow.json
- HTML version of this page: https://verifymcp.io/servers/orhansavash-zentria-flow-mcp/zentriaflow
