On va où ? Routing API MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to European route and address tools with transport-specific safety indicators: Do wheelchair and bicycle route indicators retain current provenance and clear limits rather than implying guaranteed safety?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Geocode addresses and compare safe/balanced/fast routes with surface, road, climb and turn data.

What we know

Routing MCP for European micromobility/walking. It geocodes a place and returns route alternatives with safety-relevant indicators such as cycle-lane share, unpaved surface, main-road/motorway exposure and climb.

Maintenance / activity evidence

onvaou-itineraires-mcp 0.2.0 published 2026-09-23T12:41:10.414Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read-only routing/geocoding.
Routing API key.
Sensitive access: Location/travel intent

No physical control or booking authority; location queries can still be sensitive.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do wheelchair and bicycle route indicators retain current provenance and clear limits rather than implying guaranteed safety?

The bounded review of the publisher's documented European route and address tools with transport-specific safety indicators and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

No physical control or booking authority; location queries can still be sensitive.
Read-only routing/geocoding.
Routing API key.
Origin/destination and mobility preferences are sent to routing API.
Sensitive access: Location/travel intent
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact API-key env var name
Routing/safety indicators are advisory and may not reflect live hazards.
API key/rate limits apply.
No booking or vehicle control is performed.

Original activity observations

onvaou-itineraires-mcp 0.2.0 published 2026-09-23T12:41:10.414Z

Technical identity

npm/onvaou-itineraires-mcp

Exact implementation source: https://www.npmjs.com/package/onvaou-itineraires-mcp ↗
Reviewed resource type: MCP Server
Repository identity: onvaou-app/onvaou-itineraires-mcp
Package identity: npm:onvaou-itineraires-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
onvaou-itineraires-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
console.onvaou.app
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
onvaou-app/onvaou-itineraires-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npx -y onvaou-itineraires-mcp
Configure / authenticate
MCP100 setup guide
Register stdio command in MCP client and set OVO_API_KEY; publisher shows `claude mcp add -e OVO_API_KEY=... onvaou-itineraires -- npx -y onvaou-itineraires-mcp`.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: Free API key from console.onvaou.app.
Check connection
Suggested check
Confirm route search tools in client; use read-only itinerary query.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `onvaou-itineraires-mcp` in Claude Code, remove its exact client entry with `claude mcp remove onvaou-itineraires-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove onvaou-itineraires-mcp

Official Documentation & Sources

What it does

Routing MCP for European micromobility/walking. It geocodes a place and returns route alternatives with safety-relevant indicators such as cycle-lane share, unpaved surface, main-road/motorway exposure and climb.

Capability: Search & Web
Resource type: MCP Server
Industry: Travel, Transportation & Aviation
Best fit: Geocode addresses and compare safe/balanced/fast routes with surface, road, climb and turn data.

Representative uses

Geocode place names
Find bike/e-bike/scooter/motorcycle/wheelchair/walking routes
Compare safe/balanced/fast alternatives
Inspect turn-by-turn and surface/safety indicators

Limitations

Routing/safety indicators are advisory and may not reflect live hazards.
API key/rate limits apply.
No booking or vehicle control is performed.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Routing API key.
Permissions: Read-only routing/geocoding.
Data handling: Origin/destination and mobility preferences are sent to routing API.
Cost: freemium
Risk and cautions: No physical control or booking authority; location queries can still be sensitive.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Location/travel intent
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Geocode place names; Find bike/e-bike/scooter/motorcycle/wheelchair/walking routes; Compare safe/balanced/fast alternatives; Inspect turn-by-turn and surface/safety indicators.

What authentication is documented?

Free API key from console.onvaou.app.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read-only routing/geocoding.

What data-handling boundary should I consider?

Origin/destination and mobility preferences are sent to routing API. Recorded sensitive-access context: Location/travel intent.

What limitations and risks should I check before use?

No physical control or booking authority; location queries can still be sensitive. Routing/safety indicators are advisory and may not reflect live hazards. API key/rate limits apply. No booking or vehicle control is performed. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.