US tariff layers by HTS code and origin, origin comparison, HTSUS search and landed cost.
Connect Runs on your machine
claude mcp add zentria-flow-mcp -e ZENTRIA_API_KEY=<ZENTRIA_API_KEY> -e ZENTRIA_API_BASE=<ZENTRIA_API_BASE> -- docker run -i --rm ghcr.io/orhansavash/zentria-flow-mcp:0.2.0
{
"mcpServers": {
"zentria-flow-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/orhansavash/zentria-flow-mcp:0.2.0"
],
"env": {
"ZENTRIA_API_KEY": "<ZENTRIA_API_KEY>",
"ZENTRIA_API_BASE": "<ZENTRIA_API_BASE>"
}
}
}
}
{
"mcpServers": {
"zentria-flow-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/orhansavash/zentria-flow-mcp:0.2.0"
],
"env": {
"ZENTRIA_API_KEY": "<ZENTRIA_API_KEY>",
"ZENTRIA_API_BASE": "<ZENTRIA_API_BASE>"
}
}
}
}
{
"servers": {
"zentria-flow-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/orhansavash/zentria-flow-mcp:0.2.0"
],
"env": {
"ZENTRIA_API_KEY": "<ZENTRIA_API_KEY>",
"ZENTRIA_API_BASE": "<ZENTRIA_API_BASE>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
ZENTRIA_API_KEYOptional, secret | Zentria Flow API key (starts with zf_live_). Only the landed_cost tool needs it; the three tariff tools work without a key. |
ZENTRIA_API_BASEOptional | API base URL. Default: https://zentriaflow.com |
Details
| Package | ghcr.io/orhansavash/zentria-flow-mcp:0.2.0 (OCI, stdio) |
| First published | 14 Nov 2026 |
| Last updated | 14 Nov 2026 |
| Registry name | io.github.orhansavash/zentria-flow-mcp |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
