On va où ? Routing API
NPM · ONVAOU-ITINERAIRES-MCP
Address geocoding and bike, scooter, motorcycle, wheelchair and walking routes across Europe.
Available components
Last scanned (16 hours ago)
Scores higher than 53% of npm servers
Category Maps and Location
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Nov 26 +1
- Stability: 0.97 → pass security
- 17 Nov 26 −1
- Stability: pass → 0.97 functional
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/onvaou-itineraires-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compute_route Compute a bike, scooter, motorcycle, wheelchair or walking route (Europe) ~310
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.
| Name | Type | Req | Description |
|---|---|---|---|
| avoid | array | – | ferries, steps; tolls and highways (moto); unpaved and steep (wheelchair) |
| destination | object | yes | 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 | yes | Start point |
| variants | array | – | Which variants to return (default: all three) |
| waypoints | array | – | Up to 8 intermediate stops, in order |
No output schema declared.
No examples provided.
geocode_address Find the coordinates of an address or a place (Europe) ~432
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Address, place name or point of interest, 2 to 200 characters, for example "10 rue de Rivoli, Paris" or "Gare de Rennes" |
No output schema declared.
No examples provided.
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.
npm · onvaou-itineraires-mcp
claude mcp add app-onvaou-itineraires -- npx -y onvaou-itineraires-mcp
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 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 21 November 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.
What did VerifyMCP test on the On va où ? Routing API MCP server?
VerifyMCP ran 16 checks on On va où ? Routing API, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.