Tomtom
NPM · @PIPEWORX/MCP-TOMTOM · 2 COMPONENTS
TomTom MCP — wraps the TomTom Search & Routing APIs (api.tomtom.com)
Available components
Last scanned (6 hours 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-tomtom). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
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.
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-tomtom@0.2.0
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-tomtom |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-tomtom/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560505986 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:59c04ee409591baa380830cc9028b0156cc2b556c49c17b0f38ecc502a908231204e38b9c7e8a898cd510e780e2e8d6acfd34756a7deccf0b5cadd86f |
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 →
geocode ~145
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Address or place to geocode, e.g. "350 5th Ave, New York" or "Eiffel Tower" |
No output schema declared.
No examples provided.
reverse_geocode ~125
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 })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional — your own TomTom API key for higher limits; omit to use the shared Pipeworx key. |
| lat | number | yes | Latitude of the point to reverse geocode |
| lon | number | yes | Longitude of the point to reverse geocode |
No output schema declared.
No examples provided.
route ~182
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 })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional — your own TomTom API key for higher limits; omit to use the shared Pipeworx key. |
| from_lat | number | yes | Origin latitude |
| from_lon | number | yes | Origin longitude |
| to_lat | number | yes | Destination latitude |
| to_lon | number | yes | Destination longitude |
| travel_mode | string | – | Travel mode for traffic-aware routing (default "car") |
No output schema declared.
No examples provided.
search_poi ~226
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 })
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | POI search term, e.g. "coffee", "pizza", "gas station", "Starbucks" |
| radius | number | – | Optional search radius in meters (only used when lat/lon are provided) |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-tomtom
claude mcp add pipeworx-io-tomtom -- npx -y @pipeworx/mcp-tomtom
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.