# Trade & Logistics Evidence (remote · api.timzinin.com)

Pay-per-call shipping evidence: canal queues, tanker flows, container and carbon exceptions.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-19

## Components

- remote · `api.timzinin.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-timzinin-api-trade-logistics/mcp-trade-logistics.md), [page](https://verifymcp.io/servers/com-timzinin-api-trade-logistics/mcp-trade-logistics)

## Channel facts

- Endpoint: `https://api.timzinin.com/mcp/trade-logistics`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1910 tokens (~318/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-timzinin-api-trade-logistics https://api.timzinin.com/mcp/trade-logistics
```

### Codex

```toml
[mcp_servers.com-timzinin-api-trade-logistics]
url = "https://api.timzinin.com/mcp/trade-logistics"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-timzinin-api-trade-logistics": {
      "type": "remote",
      "url": "https://api.timzinin.com/mcp/trade-logistics",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-timzinin-api-trade-logistics --url https://api.timzinin.com/mcp/trade-logistics --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-timzinin-api-trade-logistics:
    url: "https://api.timzinin.com/mcp/trade-logistics"
```

### Other

```json
{
  "mcpServers": {
    "com-timzinin-api-trade-logistics": {
      "type": "http",
      "url": "https://api.timzinin.com/mcp/trade-logistics"
    }
  }
}
```

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-08-18 (score 68, +1)

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

### 2026-08-16 (score 67, +7)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 287 → 318
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: excellent → good
- [cosmetic] Tool “container-exception-evidence” changed its title: Container Delay & Free-Time Evidence Monitor
- [cosmetic] Tool “panama-canal-queue-transit-imbalance” changed its title: Panama Canal Queue & Transit Imbalance Monitor
- [cosmetic] Tool “pricing_info” changed its title: Pricing — Trade & Logistics Evidence
- [cosmetic] Tool “singapore-bunker-tanker-divergence” changed its title: Singapore Bunker Demand & Tanker Flow Divergence
- [cosmetic] Tool “strait-of-hormuz-tanker-flow-recovery” changed its title: Strait of Hormuz Tanker Flow Recovery Index
- [cosmetic] Tool “voyage-carbon-compliance-evidence” changed its title: EU ETS Voyage Carbon Exposure Evidence

### 2026-08-15 (score 60)

First indexed and scored.

## MCP tools (6)

### `pricing_info` (~44 tokens)

Pricing — Trade & Logistics Evidence

Free — list every paid tool in the 'trade-logistics' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.

### `container-exception-evidence` (~405 tokens)

Container Delay & Free-Time Evidence Monitor

Turn buyer-authorized container event snapshots into deterministic ETA, milestone, free-time, cost-exposure, confidence, limitation, and human-review evidence. No carrier scraping, reference fetching, legal verdict, automatic claim, or provider key. — $0.02/call, x402 (USDC on base).

Input parameters:

- `containers` (array, required): At least one and at most 1,000 closed records. Snapshot accepts customer containers; synthetic_demo accepts exactly one fixed Actor-owned Synthetic Ocean record and rejects substitutions before effec…
- `continuationState` (object): Optional exact nextContinuationState from a previous successful complete run. The Actor does not store this state in a named KVS; pass it back to compare the next customer snapshot.
- `events` (array, required): At least one and at most 50,000 events. Snapshot accepts customer events; synthetic_demo accepts exactly the two fixed Actor-owned events in the public fixture and rejects substitutions or extra rows…
- `mode` (string, required): Use snapshot for customer events or synthetic_demo for the one exact canonical zero-provider public example. The demo accepts only the published fixture values; runtime rejects any changed field, ext…
- `rightsAttestation` (object, required): Required customer declaration. Apify Input Schema v1 can serialize false here; the Actor runtime requires all three declarations to be exactly true and rejects otherwise before provider, Dataset, bil…
- `sourceStatus` (string, required): Declare whether this customer-supplied snapshot is complete, partial, or unavailable.
- `tariffAssumptions` (object, required): Customer-supplied USD/day assumptions. No terminal calendar or carrier tariff is fetched.
- `watchId` (string, required): Stable identifier for one customer-owned monitoring series.

### `panama-canal-queue-transit-imbalance` (~378 tokens)

Panama Canal Queue & Transit Imbalance Monitor

Compare aggregate commercial-vessel pressure across two fixed Panama Canal approach zones. Get side imbalance, movement, observed dwell, baseline change, freshness, confidence, gaps, and a human review action without exposing raw vessel identities or claiming official Canal queues. — $0.02/call, x402 (USDC on base).

Input parameters:

- `baselineDays` (integer): Number of stored observations used for the queue baseline.
- `datalasticApiKey` (string): Required only for datalastic mode. Runtime validation requires a printable 8-256 character secret. Never returned in output.
- `identitySalt` (string): Optional HMAC salt for datalastic mode. Runtime validation requires a printable 8-256 character secret. Never returned in output.
- `maxProviderRequests` (integer): Fixed exact cap: /stat plus the two Panama approach zones.
- `maxTotalChargeUsd` (number): Buyer-side cap checked before the paid report event.
- `maxVessels` (integer): Maximum bounded provider rows accepted for each fixed approach. The live-safe default of 500 avoids truncating dense approach snapshots.
- `requestId` (string, required): Use auto for a trusted-run-derived id or provide an explicit idempotency value. The returned requestId is an irreversible SHA-256-derived identifier.
- `schemaVersion` (string, required): Contract version for this Actor input.
- `sourceMode` (string, required): Demo writes one synthetic row with no $0.05 result-found fee; the $0.005 start charge applies. Datalastic uses your own API key.
- `timeoutMs` (integer): Timeout for each bounded provider request.
- `watchId` (string, required): Stable lower-case identity for the queue history. It is irreversibly derived before lock, state, ledger, and output use.

### `singapore-bunker-tanker-divergence` (~293 tokens)

Singapore Bunker Demand & Tanker Flow Divergence

Compare official monthly Singapore bunker demand, tanker arrivals, fuel mix, and vessel calls in one evidence report. Add optional bounded BYOK tanker pressure, with publication lag, freshness, confidence, null reasons, provenance, gaps, and human review. — $0.02/call, x402 (USDC on base).

Input parameters:

- `baselineMonths` (integer): Historical window used for 3-month and 12-month comparisons.
- `datalasticApiKey` (string): Only valid with sourceMode=open_plus_byok; runtime validation requires a printable 8-256 character secret, rejects it in demo/open, and never returns it.
- `maxProviderRequests` (integer): Exactly two requests are permitted for BYOK: /stat plus the Singapore zone.
- `maxRows` (integer): One bounded page per official source; 240 covers the observed 13-month window and up to 500 is allowed.
- `maxTotalChargeUsd` (number): Buyer cap checked before the paid result event.
- `requestId` (string): Use auto for a Task-safe run identity.
- `schemaVersion` (string, required): Contract version for this Actor input.
- `sourceMode` (string): Demo is synthetic; open uses data.gov.sg; open_plus_byok adds two bounded Datalastic provider requests: /stat plus Singapore.
- `watchId` (string): Stable identity for the Singapore baseline.

### `strait-of-hormuz-tanker-flow-recovery` (~309 tokens)

Strait of Hormuz Tanker Flow Recovery Index

Compare aggregate commercial-tanker observations across three fixed Strait of Hormuz zones with seven- and thirty-observation baselines. Get deterministic recovery labels, freshness, confidence, gaps, and a human-review action without exposing raw identities or positions. — $0.02/call, x402 (USDC on base).

Input parameters:

- `datalasticApiKey` (string): Required only for live Datalastic mode. Runtime validation requires a non-empty secret, and the value is never returned in output.
- `identitySalt` (string): Optional stable secret for identity continuity across Datalastic API-key rotation. Runtime validation requires 32-256 characters; changing it starts an incompatible state epoch.
- `maxProviderRequests` (integer): Exactly four actual provider attempts/pages: one /stat and one bounded page per fixed zone.
- `maxTotalChargeUsd` (number): Buyer-side cap checked before the paid report event.
- `maxVessels` (integer): Maximum bounded provider rows accepted for each fixed zone.
- `requestId` (string): Use auto for a trusted run-derived identifier or provide an explicit idempotency value.
- `schemaVersion` (string, required): Contract version for this Actor input.
- `sourceMode` (string, required): Demo is synthetic, includes no $0.05 result-found fee, and still incurs the automatic start charge. Datalastic uses your own API key.
- `watchId` (string, required): Stable lowercase identifier for one monitoring series.

### `voyage-carbon-compliance-evidence` (~298 tokens)

EU ETS Voyage Carbon Exposure Evidence

Calculate deterministic EU ETS voyage exposure from buyer-supplied vessel, route, and fuel facts using pinned official fixtures. Get gas, fuel, segment, truth-ledger, confidence, limitation, and receipt evidence without provider calls or an automatic legal decision. — $0.02/call, x402 (USDC on base).

Input parameters:

- `berthRecords` (array, required): Optional array of up to 18 berth fuel-consumption records linked to port calls. Supply an empty array when no berth consumption evidence is available.
- `legs` (array, required): Ordered array of 1–8 voyage legs linking the supplied port calls. Each leg includes its UTC interval and bounded fuel-consumption evidence.
- `mode` (string, required): Choose `decision` for buyer-supplied voyage facts or `synthetic_demo` for the fixed no-charge example. Runtime enforces the fields allowed in each mode.
- `portCalls` (array, required): Ordered array of 2–9 buyer-supplied port-call facts. IDs must be unique and are referenced by voyage legs and optional berth-consumption records.
- `requestId` (string, required): Buyer correlation ID copied into the evidence receipt. Decision mode requires `rq_` plus 32 lowercase hexadecimal characters; demo mode uses `public-demo-v1`.
- `schemaVersion` (string, required): Contract version for validation and output interpretation. Enter `1.1.0`; other values are rejected before any Dataset delivery.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-timzinin-api-trade-logistics/mcp-trade-logistics#diagnostics

## Score history

- 2026-08-19: 68
- 2026-08-18: 68
- 2026-08-17: 67
- 2026-08-16: 67
- 2026-08-15: 60

## Links

- Remote endpoint: https://api.timzinin.com/mcp/trade-logistics
- Changelog RSS feed: https://verifymcp.io/servers/com-timzinin-api-trade-logistics/mcp-trade-logistics.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-timzinin-api-trade-logistics/mcp-trade-logistics.json
- HTML version of this page: https://verifymcp.io/servers/com-timzinin-api-trade-logistics/mcp-trade-logistics