# On va où ? Routing API (npm · onvaou-itineraires-mcp)

Address geocoding and bike, scooter, motorcycle, wheelchair and walking routes across Europe.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- npm · `onvaou-itineraires-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/app-onvaou-itineraires/onvaou-itineraires-mcp.md), [page](https://verifymcp.io/servers/app-onvaou-itineraires/onvaou-itineraires-mcp)

## Channel facts

- Registry: `npm`
- Package: `onvaou-itineraires-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-09-26.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 742 tokens (~371/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the On va où ? Routing API MCP server?

On va où ? Routing API runs locally as an npm package, launched with npx -y onvaou-itineraires-mcp. 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 app-onvaou-itineraires -- npx -y onvaou-itineraires-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "app-onvaou-itineraires": {
      "command": "npx",
      "args": [
        "-y",
        "onvaou-itineraires-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-onvaou-itineraires": {
      "command": "npx",
      "args": [
        "-y",
        "onvaou-itineraires-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add app-onvaou-itineraires -- npx -y onvaou-itineraires-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-onvaou-itineraires": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "onvaou-itineraires-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-onvaou-itineraires --command npx --arg -y --arg onvaou-itineraires-mcp
```

### Hermes

```yaml
mcp_servers:
  app-onvaou-itineraires:
    command: "npx"
    args: ["-y", "onvaou-itineraires-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "app-onvaou-itineraires": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "onvaou-itineraires-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-onvaou-itineraires -t stdio -c npx -a -y onvaou-itineraires-mcp
```

### Other

```json
{
  "mcpServers": {
    "app-onvaou-itineraires": {
      "command": "npx",
      "args": [
        "-y",
        "onvaou-itineraires-mcp"
      ]
    }
  }
}
```

## 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-09-26 (score 69, +1)

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

### 2026-09-25 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 68, +1)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Schema quality: 287 → 371
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.1 → 0.2.0

### 2026-09-22 (score 67, +10)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-09-21 (score 57)

First indexed and scored.

## MCP tools (2)

### `compute_route` (~310 tokens)

Compute a bike, scooter, motorcycle, wheelchair or walking route (Europe)

Computes up to three routes (safe, balanced, fast) between two points in Europe for a bike, e-bike, kick scooter, motorcycle, wheelchair or on foot, with the share of cycle lanes, unpaved surfaces, main roads and motorways, the climb, and turn-by-turn steps. Use it to plan a safe cycling commute, compare a safe and a fast option, check wheelchair accessibility of a trip, or plan a motorcycle trip avoiding tolls or motorways. Points are given as longitude/latitude: when you only have an address, a place name or a station, call geocode_address first and pass the coordinates it returns.

Input parameters:

- `avoid` (array): ferries, steps; tolls and highways (moto); unpaved and steep (wheelchair)
- `destination` (object, required): End point
- `include_elevation_profile` (boolean): Include the elevation profile (up to 100 points)
- `include_geometry` (boolean): Include the encoded polyline (Google algorithm, precision 5)
- `include_steps` (boolean): Include turn-by-turn instructions
- `language` (string): Language of the turn-by-turn instructions
- `mode` (string): bike, ebike, scooter (kick scooter), moto (motorcycle), wheelchair, foot
- `origin` (object, required): Start point
- `variants` (array): Which variants to return (default: all three)
- `waypoints` (array): Up to 8 intermediate stops, in order

### `geocode_address` (~432 tokens)

Find the coordinates of an address or a place (Europe)

Turns an address, a place name, a station or a point of interest into longitude/latitude coordinates, which are exactly what compute_route expects as origin, destination or waypoint. Call this first whenever the user names a place instead of giving coordinates. Returns up to five candidates, best first, each with a full label, its coordinates, its type (address, street, locality, region, country, venue for a named place such as a station or a monument, or other) and a confidence score, so an ambiguous name can be disambiguated before routing. Narrow the search with `near` (bias the ranking around a point, typically the other end of the trip) or `country`. Results come from Photon (OpenStreetMap) across Europe, and from the IGN Géoplateforme in France, which hands over to Photon when it is unavailable, returns nothing, or its best confidence is below 0.4; the answer says which source served it. A search has its own daily allowance and never counts towards the monthly routing quota, so looking a place up before routing costs nothing. Coverage: Europe.

Input parameters:

- `country` (string): Restrict to one country, ISO 3166-1 alpha-2 code, for example FR or BE
- `language` (string): Language of the returned labels. en, fr and de are honoured; it is accepted but the geocoder does not label in Italian, and the labels then come back in the local language of each place (Milano, Münc…
- `limit` (integer): Number of candidates to return, 1 to 5
- `near` (object): Bias the ranking towards this point, typically the other end of the trip. It does not restrict the search, but the point itself must be inside the European coverage: anywhere else is refused with 422…
- `query` (string, required): Address, place name or point of interest, 2 to 200 characters, for example "10 rue de Rivoli, Paris" or "Gare de Rennes"

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/app-onvaou-itineraires/onvaou-itineraires-mcp#diagnostics

## Score history

- 2026-09-26: 69
- 2026-09-25: 68
- 2026-09-24: 68
- 2026-09-23: 68
- 2026-09-22: 67
- 2026-09-21: 57

## Common questions

### What is the On va où ? Routing API MCP server?

On va où ? Routing API is an MCP server listed in the public MCP registry as app.onvaou/itineraires. Address geocoding and bike, scooter, motorcycle, wheelchair and walking routes across Europe. This page covers its npm package (onvaou-itineraires-mcp).

### Is the On va où ? Routing API MCP server safe to use?

On va où ? Routing API scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. 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 On va où ? Routing API MCP server expose?

On va où ? Routing API exposes 2 tools: compute_route, geocode_address. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.

### Is the On va où ? Routing API MCP server still maintained?

On va où ? Routing API is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the On va où ? Routing API MCP server under?

On va où ? Routing API declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/onvaou-itineraires-mcp
- Socket report: https://socket.dev/npm/package/onvaou-itineraires-mcp
- Repository: https://github.com/onvaou-app/onvaou-itineraires-mcp
- Website: https://onvaou.app/developers/routing-api.html
- Changelog RSS feed: https://verifymcp.io/servers/app-onvaou-itineraires/onvaou-itineraires-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-onvaou-itineraires/onvaou-itineraires-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-onvaou-itineraires/onvaou-itineraires-mcp