# Raute Route Planner (remote · www.raute.io)

Plans delivery routes for up to 25 US addresses and 5 drivers, with the stop order and a map.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.raute.io`: 83/100 (this document), [markdown](https://verifymcp.io/servers/io-raute-route-planner/api-mcp-mcp.md), [page](https://verifymcp.io/servers/io-raute-route-planner/api-mcp-mcp)

## Channel facts

- Endpoint: `https://www.raute.io/api/mcp/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-05.

- **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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 344 tokens (~172/item across 2 items; 1 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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).
  - Supports UI / widget rendering.

## Install

### How do I install the Raute Route Planner MCP server?

Raute Route Planner is a hosted endpoint at https://www.raute.io/api/mcp/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 io-raute-route-planner 'https://www.raute.io/api/mcp/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "io-raute-route-planner": {
      "url": "https://www.raute.io/api/mcp/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-raute-route-planner": {
      "type": "http",
      "url": "https://www.raute.io/api/mcp/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-raute-route-planner]
url = "https://www.raute.io/api/mcp/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-raute-route-planner": {
      "type": "remote",
      "url": "https://www.raute.io/api/mcp/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-raute-route-planner --url 'https://www.raute.io/api/mcp/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-raute-route-planner:
    url: "https://www.raute.io/api/mcp/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "io-raute-route-planner": {
      "Transport": "http",
      "Url": "https://www.raute.io/api/mcp/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-raute-route-planner -t streamable-http -u 'https://www.raute.io/api/mcp/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "io-raute-route-planner": {
      "type": "http",
      "url": "https://www.raute.io/api/mcp/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-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-10-31 (score 81, +1)

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

### 2026-10-29 (score 80, +1)

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

### 2026-10-27 (score 79, +1)

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

### 2026-10-25 (score 78, +1)

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

### 2026-10-23 (score 77, +1)

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

### 2026-10-21 (score 76, +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.

## MCP tools (1)

### `plan_delivery_route` (~256 tokens)

Plan a delivery route

Puts a list of US delivery addresses in the best driving order for one driver, or splits them across up to 5 drivers, and shows the routes on a map. Suited to anyone with several stops to deliver to or visit who wants the fastest order or a fair split between drivers. Takes up to 25 street addresses, an optional start address and an optional return to the start. Returns each driver's stops in order with miles and minutes, and names any address it could not place. US addresses only; it plans the order of stops and does not give turn by turn directions.

Input parameters:

- `drivers` (integer): How many drivers to split the stops between. Defaults to 1.
- `goal` (string): With several drivers: fewest_miles keeps total driving lowest, even_load spreads the day's work more evenly between drivers.
- `return_to_start` (boolean): True if the drivers come back to the start at the end.
- `start` (string): Where the driver or drivers start, such as the warehouse or shop. If left out, the first address is the start.
- `stops` (array, required): The delivery addresses, as the person wrote them. Street, city and state, with ZIP if known.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-raute-route-planner/api-mcp-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74

## Common questions

### What is the Raute Route Planner MCP server?

Raute Route Planner is an MCP server listed in the public MCP registry as io.raute/route-planner. Plans delivery routes for up to 25 US addresses and 5 drivers, with the stop order and a map. This page covers its hosted endpoint (https://www.raute.io/api/mcp/mcp/).

### Is the Raute Route Planner MCP server safe to use?

Raute Route Planner scores 83 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 Raute Route Planner MCP server expose?

Raute Route Planner exposes 1 tool: plan_delivery_route. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.

### Does the Raute Route Planner MCP server require authentication?

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

### Is the Raute Route Planner MCP server still maintained?

Raute Route Planner is still listed as active in the MCP registry. We last reached this channel on 5 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 Raute Route Planner MCP server?

VerifyMCP ran 14 checks on Raute Route Planner, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://www.raute.io/api/mcp/mcp/
- Website: https://www.raute.io/ai-assistants/
- Changelog RSS feed: https://verifymcp.io/servers/io-raute-route-planner/api-mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-raute-route-planner/api-mcp-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-raute-route-planner/api-mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-raute-route-planner/api-mcp-mcp