Openrouteservice
NPM · @PIPEWORX/MCP-OPENROUTESERVICE · 2 COMPONENTS
Openrouteservice MCP.
Available components
Last scanned (1 day ago)
Scores higher than 61% 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openrouteservice). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1034 tokens (~147/item across 7 items; 7 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 77
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-openrouteservice@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-openrouteservice |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-openrouteservice/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685147778 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8f8ff74a9a4811bfffafc340c0dfd527cb99488e84b41325a4a7af28b2c60f68d52471c27e724d8be9288cdbe7c8cece83ec5792b045fdb7b6b24f1a6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
directions ~189
"Directions from A to B" / "how far is [X] from [Y]" / "hiking / cycling / wheelchair / walking route" / "truck routing" / "HGV directions" / "driving route" — turn-by-turn routing between coordinates with profile-specific routing. Profiles: driving-car, driving-hgv (trucks), foot-walking, foot-hiking, cycling-regular / mountain / road / electric, wheelchair. Returns geometry, distance, duration, turn-by-turn instructions, elevation. Uses OpenStreetMap data via OpenRouteService. Use for hiking/biking/wheelchair/truck cases where Mapbox/Google don't have the right profile.
| Name | Type | Req | Description |
|---|---|---|---|
| coordinates | array | yes | [[lon, lat], …] |
| format | string | – | json (default) | geojson | gpx |
| instructions | boolean | – | – |
| profile | string | – | – |
No output schema declared.
No examples provided.
elevation_line ~115
"Elevation profile along a route" / "hiking trail elevation gain" / "topographic profile of [path]" / "how hilly is this route" — elevation samples along a geometry (linestring). Pass geojson / polyline / encodedpolyline5 / encodedpolyline6. Use for hiking elevation gain, cycling grade analysis, trail planning, terrain profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| format_in | string | yes | geojson | polyline | encodedpolyline5 | encodedpolyline6 |
| geometry | – | yes | Per format_in |
No output schema declared.
No examples provided.
elevation_point ~96
"Elevation / altitude at [coordinates]" / "how high is [location]" / "height above sea level for [lat,lng]" — elevation (meters above sea level) at a single point. Use for "what's the elevation of Denver", terrain queries, or attaching altitude to GPS records.
| Name | Type | Req | Description |
|---|---|---|---|
| format_in | string | yes | point | geojson |
| geometry | – | yes | Per format_in (point: [lon, lat]) |
No output schema declared.
No examples provided.
geocode_search ~149
"Geocode [address]" / "find [city] coordinates" / "search for places named [X]" / "where is [landmark]" — geocode an address or place name to coordinates via Pelias (OpenStreetMap-backed). Returns ranked candidates with lat/lng, address components, layer (venue/street/locality/region). Use as a free alternative to Mapbox/Google geocoding, or when you want OpenStreetMap-curated data.
| Name | Type | Req | Description |
|---|---|---|---|
| focus_lat | number | – | – |
| focus_lon | number | – | – |
| layers | string | – | – |
| size | number | – | – |
| sources | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
isochrones ~131
"Reachable area in [N] minutes" / "drive-time / walk-time / bike-time polygons" / "service area" / "catchment polygon" / "isochrone map" — generate isochrone polygons (area reachable from a point in time or distance) for car / truck / bike / foot / wheelchair profiles using OpenStreetMap. Use for delivery zones, commute sheds, site selection.
| Name | Type | Req | Description |
|---|---|---|---|
| locations | array | yes | – |
| profile | string | – | – |
| range | array | yes | Seconds or meters. |
| range_type | string | – | time (default) | distance |
No output schema declared.
No examples provided.
matrix ~199
"Distance matrix between locations" / "all-to-all travel times" / "N×M routing grid" / "drive / walk / bike times between [list]" — N×M distance and duration matrix between many points via OpenStreetMap routing. Use for traveling-salesman setup, multi-stop optimization, nearest-warehouse, fleet dispatch. Profile-aware (car / truck / bike / foot / wheelchair).
| Name | Type | Req | Description |
|---|---|---|---|
| destinations | array | – | Which `locations` to route TO, as 0-based indices into that array — e.g. [1,2]. NOT coordinates. Omit to use every location. |
| locations | array | yes | – |
| metrics | array | – | ["duration","distance"] |
| profile | string | – | – |
| sources | array | – | Which `locations` to route FROM, as 0-based indices into that array — e.g. [0] means the first location. NOT coordinates. Omit to use every location. |
No output schema declared.
No examples provided.
snap ~101
"Snap coordinate to nearest road" / "find closest road to [lat,lng]" / "is there a road at this point" — snap arbitrary GPS coordinates to the nearest routable OSM road for a given profile (car / bike / foot). Use to clean noisy GPS, validate routability before calling directions, or place markers on a road network.
| Name | Type | Req | Description |
|---|---|---|---|
| locations | array | yes | – |
| profile | string | – | – |
| radius | number | – | – |
No output schema declared.
No examples provided.
How do I install the Openrouteservice MCP server?
Openrouteservice runs locally as an npm package, launched with npx -y @pipeworx/mcp-openrouteservice. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-openrouteservice
claude mcp add pipeworx-io-openrouteservice -- npx -y @pipeworx/mcp-openrouteservice
What is the Openrouteservice MCP server?
Openrouteservice is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openrouteservice. Openrouteservice MCP. This page covers its npm package (@pipeworx/mcp-openrouteservice).
Is the Openrouteservice MCP server safe to use?
Openrouteservice scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Openrouteservice MCP server expose?
Openrouteservice exposes 7 tools: directions, matrix, isochrones, snap, elevation_line, and 2 more. Their descriptions and schemas cost roughly 980 tokens of context every time the server is loaded.
Is the Openrouteservice MCP server still maintained?
Openrouteservice is still listed as active in the MCP registry. We last reached this channel on 4 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 Openrouteservice MCP server under?
Openrouteservice declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.