Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
Trade & Logistics Evidence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Pay-per-call shipping evidence: canal queues, tanker flows, container and carbon exceptions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http trade-logistics-evidence-mcp https://api.timzinin.com/mcp/trade-logistics
# 2 — ask your agent for something these tools do
# pricing_info, container-exception-evidence, panama-canal-queue-transit-imbalance and 3 more
Trade & Logistics Evidence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TIAll 12 servers
timzinin12 servers
5 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http trade-logistics-evidence-mcp https://api.timzinin.com/mcp/trade-logisticsReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watchId | string | yes | Stable identifier for one customer-owned monitoring series. |
| mode | string | yes | 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, extr |
| sourceStatus | string | yes | Declare whether this customer-supplied snapshot is complete, partial, or unavailable. |
| rightsAttestation | object | yes | 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, bill |
| containers | array | yes | 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 effect |
| events | array | yes | 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 |
| tariffAssumptions | object | yes | Customer-supplied USD/day assumptions. No terminal calendar or carrier tariff is fetched. |
| continuationState | object | no | 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. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | yes | Contract version for this Actor input. |
| requestId | string | yes | Use auto for a trusted-run-derived id or provide an explicit idempotency value. The returned requestId is an irreversible SHA-256-derived identifier. |
| watchId | string | yes | Stable lower-case identity for the queue history. It is irreversibly derived before lock, state, ledger, and output use. |
| sourceMode | string | yes | Demo writes one synthetic row with no $0.05 result-found fee; the $0.005 start charge applies. Datalastic uses your own API key. |
| datalasticApiKey | string | no | Required only for datalastic mode. Runtime validation requires a printable 8-256 character secret. Never returned in output. |
| identitySalt | string | no | Optional HMAC salt for datalastic mode. Runtime validation requires a printable 8-256 character secret. Never returned in output. |
| baselineDays | integer | no | Number of stored observations used for the queue baseline. |
| maxVessels | integer | no | Maximum bounded provider rows accepted for each fixed approach. The live-safe default of 500 avoids truncating dense approach snapshots. |
| maxProviderRequests | integer | no | Fixed exact cap: /stat plus the two Panama approach zones. |
| timeoutMs | integer | no | Timeout for each bounded provider request. |
| maxTotalChargeUsd | number | no | Buyer-side cap checked before the paid report event. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | yes | Contract version for this Actor input. |
| requestId | string | no | Use auto for a Task-safe run identity. |
| watchId | string | no | Stable identity for the Singapore baseline. |
| sourceMode | string | no | Demo is synthetic; open uses data.gov.sg; open_plus_byok adds two bounded Datalastic provider requests: /stat plus Singapore. |
| datalasticApiKey | string | no | 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. |
| baselineMonths | integer | no | Historical window used for 3-month and 12-month comparisons. |
| maxRows | integer | no | One bounded page per official source; 240 covers the observed 13-month window and up to 500 is allowed. |
| maxProviderRequests | integer | no | Exactly two requests are permitted for BYOK: /stat plus the Singapore zone. |
| maxTotalChargeUsd | number | no | Buyer cap checked before the paid result event. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | yes | Contract version for this Actor input. |
| requestId | string | no | Use auto for a trusted run-derived identifier or provide an explicit idempotency value. |
| watchId | string | yes | Stable lowercase identifier for one monitoring series. |
| sourceMode | string | yes | Demo is synthetic, includes no $0.05 result-found fee, and still incurs the automatic start charge. Datalastic uses your own API key. |
| datalasticApiKey | string | no | Required only for live Datalastic mode. Runtime validation requires a non-empty secret, and the value is never returned in output. |
| identitySalt | string | no | Optional stable secret for identity continuity across Datalastic API-key rotation. Runtime validation requires 32-256 characters; changing it starts an incompatible state epoch. |
| maxVessels | integer | no | Maximum bounded provider rows accepted for each fixed zone. |
| maxProviderRequests | integer | no | Exactly four actual provider attempts/pages: one /stat and one bounded page per fixed zone. |
| maxTotalChargeUsd | number | no | Buyer-side cap checked before the paid report event. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | yes | Contract version for validation and output interpretation. Enter 1.1.0; other values are rejected before any Dataset delivery. |
| mode | string | yes | Choose decision for buyer-supplied voyage facts or synthetic_demo for the fixed no-charge example. Runtime enforces the fields allowed in each mode. |
| requestId | string | yes | Buyer correlation ID copied into the evidence receipt. Decision mode requires rq_ plus 32 lowercase hexadecimal characters; demo mode uses public-demo-v1. |
| portCalls | array | yes | 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. |
| legs | array | yes | Ordered array of 1–8 voyage legs linking the supplied port calls. Each leg includes its UTC interval and bounded fuel-consumption evidence. |
| berthRecords | array | yes | 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. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Trade & Logistics Evidence or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest10e0a94e14cd59bc7f78f2dd2be9fb55bfdb3b08b873ce8614440badebf56dd3
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| pricing_info | no tags | |
| container-exception-evidence | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| panama-canal-queue-transit-imbalance | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| singapore-bunker-tanker-divergence | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| strait-of-hormuz-tanker-flow-recovery | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| voyage-carbon-compliance-evidence | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest10e0a94e14cd59bc
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Trade & Logistics Evidence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.