# Torivane Logistics Engine (remote · torivane.kinganlogic.com)

Shipment lifecycle assessments, reassessments, and authorized outcome reconciliation.

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: yes
- Last scored: 2026-11-21

## Components

- remote · `torivane.kinganlogic.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/com-kinganlogic-torivane-logistics-engine/torivane.md), [page](https://verifymcp.io/servers/com-kinganlogic-torivane-logistics-engine/torivane)

## Channel facts

- Endpoint: `https://torivane.kinganlogic.com/mcp`
- 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-11-21.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 42/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 836 tokens (~64/item across 13 items; 13 tools + 0 resources), lean.
  - 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**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Torivane Logistics Engine MCP server?

Torivane Logistics Engine is a hosted endpoint at https://torivane.kinganlogic.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 com-kinganlogic-torivane-logistics-engine 'https://torivane.kinganlogic.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kinganlogic-torivane-logistics-engine": {
      "url": "https://torivane.kinganlogic.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kinganlogic-torivane-logistics-engine": {
      "type": "http",
      "url": "https://torivane.kinganlogic.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kinganlogic-torivane-logistics-engine]
url = "https://torivane.kinganlogic.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-kinganlogic-torivane-logistics-engine --url 'https://torivane.kinganlogic.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kinganlogic-torivane-logistics-engine:
    url: "https://torivane.kinganlogic.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kinganlogic-torivane-logistics-engine": {
      "Transport": "http",
      "Url": "https://torivane.kinganlogic.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kinganlogic-torivane-logistics-engine -t streamable-http -u 'https://torivane.kinganlogic.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-kinganlogic-torivane-logistics-engine": {
      "type": "http",
      "url": "https://torivane.kinganlogic.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 59, +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-19 (score 58, +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-18 (score 57, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 57)

First indexed and scored.

## MCP tools (13)

### `assess_shipment` (~64 tokens)

One evidence-grounded shipment decision with source timestamps, uncertainty, limitations and an owner-scoped receipt.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `reconcile_alias` (~58 tokens)

A same-shipment alias determination with supporting evidence or an explicit evidence hold.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `diagnose_evidence` (~57 tokens)

A diagnostic of contradictions, missing evidence and the next evidence needed.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `reassess_shipment` (~70 tokens)

POST /machine/v1/shipments/{logical_shipment_id}/reassess; scope shipment:reassess

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string, required)
- `receipt_reference` (string)
- `request` (object, required)

### `reconcile_outcome` (~66 tokens)

POST /machine/v1/shipments/{logical_shipment_id}/outcomes; scope outcome:write

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string, required)
- `receipt_reference` (string)
- `request` (object, required)

### `activate_shipment` (~73 tokens)

One initial qualified assessment plus five material reassessments through delivery. Included updates, unchanged cached checks and outcome reconciliation cost $0.00 extra.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `developerEstablishedRouteIntelligence` (~66 tokens)

An owner-authorized shipment forecast with confirmed physical evidence, learned route timing, evidence freshness and uncertainty.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `developerFingerprintRouteIntelligence` (~65 tokens)

An owner-private carrier/address forecast using a mature fingerprint, with physical evidence, freshness and uncertainty.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `merchantEstablishedRouteIntelligence` (~66 tokens)

An owner-authorized shipment forecast with confirmed physical evidence, learned route timing, evidence freshness and uncertainty.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `merchantFingerprintRouteIntelligence` (~65 tokens)

An owner-private carrier/address forecast using a mature fingerprint, with physical evidence, freshness and uncertainty.

Input parameters:

- `idempotency_key` (string, required)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `quote_shipment` (~60 tokens)

POST /machine/v1/shipments/quote; scope shipment:quote

Input parameters:

- `idempotency_key` (string)
- `logical_shipment_id` (string)
- `receipt_reference` (string)
- `request` (object, required)

### `read_shipment` (~65 tokens)

GET /machine/v1/shipments/{logical_shipment_id}; scope shipment:reassess

Input parameters:

- `idempotency_key` (string)
- `logical_shipment_id` (string, required)
- `receipt_reference` (string)
- `request` (object)

### `get_receipt` (~61 tokens)

GET /machine/v1/receipts/{receipt_reference}; scope receipt:read

Input parameters:

- `idempotency_key` (string)
- `logical_shipment_id` (string)
- `receipt_reference` (string, required)
- `request` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-kinganlogic-torivane-logistics-engine/torivane#diagnostics

## Score history

- 2026-11-21: 59
- 2026-11-20: 58
- 2026-11-19: 58
- 2026-11-18: 57
- 2026-11-17: 57

## Common questions

### What is the Torivane Logistics Engine MCP server?

Torivane Logistics Engine is an MCP server listed in the public MCP registry as com.kinganlogic/torivane-logistics-engine. Shipment lifecycle assessments, reassessments, and authorized outcome reconciliation. This page covers its hosted endpoint (https://torivane.kinganlogic.com/mcp). Its publisher has verified ownership with us.

### Is the Torivane Logistics Engine MCP server safe to use?

Torivane Logistics Engine scores 59 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 Torivane Logistics Engine MCP server expose?

Torivane Logistics Engine exposes 13 tools: assess_shipment, reconcile_alias, diagnose_evidence, reassess_shipment, reconcile_outcome, and 8 more. Their descriptions and schemas cost roughly 836 tokens of context every time the server is loaded.

### Does the Torivane Logistics Engine MCP server require authentication?

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

### Is the Torivane Logistics Engine MCP server still maintained?

Torivane Logistics Engine 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 Torivane Logistics Engine MCP server?

VerifyMCP ran 12 checks on Torivane Logistics Engine, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Torivane Logistics Engine: Authorization. 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://torivane.kinganlogic.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-kinganlogic-torivane-logistics-engine/torivane.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kinganlogic-torivane-logistics-engine/torivane/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-kinganlogic-torivane-logistics-engine/torivane.json
- HTML version of this page: https://verifymcp.io/servers/com-kinganlogic-torivane-logistics-engine/torivane
