# Tomtom (npm · @pipeworx/mcp-tomtom)

TomTom MCP — wraps the TomTom Search & Routing APIs (api.tomtom.com)

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-tomtom`
- 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-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-tomtom).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 731 tokens (~182/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Tomtom MCP server?

Tomtom runs locally as an npm package, launched with npx -y @pipeworx/mcp-tomtom. 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-tomtom -- npx -y @pipeworx/mcp-tomtom
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-10-31 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `geocode` (~145 tokens)

Geocoding: convert an address, place name, or free-text location query into geographic coordinates (latitude/longitude). Returns formatted address, country, lat, lon, type, and match score. Example: geocode({ query: "350 5th Ave, New York" })

Input parameters:

- `_apiKey` (string): Optional — your own TomTom API key for higher limits; omit to use the shared Pipeworx key.
- `limit` (number): Maximum number of results to return (default 5)
- `query` (string, required): Address or place to geocode, e.g. "350 5th Ave, New York" or "Eiffel Tower"

### `search_poi` (~226 tokens)

Search for points of interest (POIs) — businesses, landmarks, restaurants, gas stations, etc. — by name or category, optionally near a lat/lon center within a radius. Returns name, category, address, coordinates, phone, url, and distance. Example: search_poi({ query: "coffee", lat: 40.748, lon: -73.985, radius: 1000 })

Input parameters:

- `_apiKey` (string): Optional — your own TomTom API key for higher limits; omit to use the shared Pipeworx key.
- `lat` (number): Optional latitude of the search center to bias/limit results
- `limit` (number): Maximum number of results to return (default 10)
- `lon` (number): Optional longitude of the search center to bias/limit results
- `query` (string, required): POI search term, e.g. "coffee", "pizza", "gas station", "Starbucks"
- `radius` (number): Optional search radius in meters (only used when lat/lon are provided)

### `reverse_geocode` (~125 tokens)

Reverse geocoding: convert latitude/longitude coordinates into a human-readable street address. Returns the freeform address, country, municipality, street name, postal code, and position. Example: reverse_geocode({ lat: 40.748, lon: -73.985 })

Input parameters:

- `_apiKey` (string): Optional — your own TomTom API key for higher limits; omit to use the shared Pipeworx key.
- `lat` (number, required): Latitude of the point to reverse geocode
- `lon` (number, required): Longitude of the point to reverse geocode

### `route` (~182 tokens)

Traffic-aware routing / directions: calculate the best route between two points and return distance plus travel time computed with live traffic. Reports traffic delay so you get realistic ETAs, not free-flow estimates. Supports car, truck, pedestrian, and bicycle travel modes. Example: route({ from_lat: 40.748, from_lon: -73.985, to_lat: 40.689, to_lon: -74.044 })

Input parameters:

- `_apiKey` (string): Optional — your own TomTom API key for higher limits; omit to use the shared Pipeworx key.
- `from_lat` (number, required): Origin latitude
- `from_lon` (number, required): Origin longitude
- `to_lat` (number, required): Destination latitude
- `to_lon` (number, required): Destination longitude
- `travel_mode` (string): Travel mode for traffic-aware routing (default "car")

## Diagnostics

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

## Score history

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

## Common questions

### What is the Tomtom MCP server?

Tomtom is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tomtom. TomTom MCP, wraps the TomTom Search & Routing APIs (api.tomtom.com). This page covers its npm package (@pipeworx/mcp-tomtom).

### Is the Tomtom MCP server safe to use?

Tomtom scores 79 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 Tomtom MCP server expose?

Tomtom exposes 4 tools: geocode, search_poi, reverse_geocode, route. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.

### Is the Tomtom MCP server still maintained?

Tomtom 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 Tomtom MCP server under?

Tomtom 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-tomtom
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-tomtom
- Repository: https://github.com/pipeworx-io/mcp-tomtom
- Website: https://pipeworx.io/packs/tomtom
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-tomtom/pipeworx-mcp-tomtom.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-tomtom/pipeworx-mcp-tomtom.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-tomtom/pipeworx-mcp-tomtom