# Openrouteservice (npm · @pipeworx/mcp-openrouteservice)

Openrouteservice MCP.

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

## Components

- remote · `gateway.pipeworx.io`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-openrouteservice/openrouteservice-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-openrouteservice/openrouteservice-mcp)
- npm · `@pipeworx/mcp-openrouteservice`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-openrouteservice/pipeworx-mcp-openrouteservice.md), [page](https://verifymcp.io/servers/pipeworx-io-openrouteservice/pipeworx-mcp-openrouteservice)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-openrouteservice`
- Version: `0.2.1`
- 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-11-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openrouteservice).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 42% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 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.

### Claude

```bash
claude mcp add pipeworx-io-openrouteservice -- npx -y @pipeworx/mcp-openrouteservice
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-openrouteservice": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openrouteservice"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-openrouteservice": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openrouteservice"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-openrouteservice -- npx -y @pipeworx/mcp-openrouteservice
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-openrouteservice": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-openrouteservice"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-openrouteservice --command npx --arg -y --arg @pipeworx/mcp-openrouteservice
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-openrouteservice:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-openrouteservice"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-openrouteservice": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-openrouteservice"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-openrouteservice -t stdio -c npx -a -y @pipeworx/mcp-openrouteservice
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-openrouteservice": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openrouteservice"
      ]
    }
  }
}
```

## 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 80, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 79, +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.

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

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (7)

### `directions` (~189 tokens)

"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.

Input parameters:

- `coordinates` (array, required): [[lon, lat], …]
- `format` (string): json (default) | geojson | gpx
- `instructions` (boolean)
- `profile` (string)

### `matrix` (~199 tokens)

"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).

Input parameters:

- `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, required)
- `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.

### `isochrones` (~131 tokens)

"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.

Input parameters:

- `locations` (array, required)
- `profile` (string)
- `range` (array, required): Seconds or meters.
- `range_type` (string): time (default) | distance

### `snap` (~101 tokens)

"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.

Input parameters:

- `locations` (array, required)
- `profile` (string)
- `radius` (number)

### `elevation_line` (~115 tokens)

"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.

Input parameters:

- `format_in` (string, required): geojson | polyline | encodedpolyline5 | encodedpolyline6
- `geometry` (required): Per format_in

### `elevation_point` (~96 tokens)

"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.

Input parameters:

- `format_in` (string, required): point | geojson
- `geometry` (required): Per format_in (point: [lon, lat])

### `geocode_search` (~149 tokens)

"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.

Input parameters:

- `focus_lat` (number)
- `focus_lon` (number)
- `layers` (string)
- `size` (number)
- `sources` (string)
- `text` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77

## Common questions

### 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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 5 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-openrouteservice
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-openrouteservice
- Repository: https://github.com/pipeworx-io/mcp-openrouteservice
- Website: https://pipeworx.io/packs/openrouteservice
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-openrouteservice/pipeworx-mcp-openrouteservice.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-openrouteservice/pipeworx-mcp-openrouteservice.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-openrouteservice/pipeworx-mcp-openrouteservice