Google_maps
NPM · @PIPEWORX/MCP-GOOGLE_MAPS · 2 COMPONENTS
Google Maps MCP Pack — geocoding, places, directions, distance matrix, elevation. Uses Google Maps…
Available components
Last scanned (3 hours ago)
Scores higher than 76% 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-google_maps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 966 tokens (~138/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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-google_maps@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-google_maps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-google_maps/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637334273 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:920ff672997dfea6527863bdab54a94a570c78ed8e87d90163946bfb88d17e99bd1e4c1325d04b1fd9820492464e494c6f7b603b026e76215bdae0a39 |
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 →
maps_directions ~171
"Google Maps directions from A to B" / "transit / public-transport directions" / "bus / subway / train route" / "best way to get from [X] to [Y]" — turn-by-turn directions via Google Maps. Modes: driving, walking, transit (bus/subway/train), bicycling. Requires Google Maps API key. PREFER over Mapbox/OpenRouteService specifically for public-transit routing — Google has the best transit data.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Google Maps API key |
| destination | string | yes | End point (address or "lat,lng") |
| mode | string | – | Travel mode: driving, walking, bicycling, transit (default: driving) |
| origin | string | yes | Starting point (address or "lat,lng") |
No output schema declared.
No examples provided.
maps_distance_matrix ~149
"Travel time matrix between [N] origins and [M] destinations" / "drive-time grid via Google Maps" / "transit times between addresses" — N×M distance and duration matrix between many points via Google Maps. Modes: driving, walking, bicycling, transit. Use for delivery routing, multi-stop optimization, transit-heavy planning.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Google Maps API key |
| destinations | string | yes | Pipe-separated destinations (e.g., "Philadelphia|Washington DC") |
| mode | string | – | Travel mode: driving, walking, bicycling, transit |
| origins | string | yes | Pipe-separated origins (e.g., "New York|Boston") |
No output schema declared.
No examples provided.
maps_elevation ~106
"Elevation at [coords] via Google" / "altitude / height above sea level" — elevation in meters for one or more lat/lng pairs via Google Maps Elevation API. Pipe-separated locations for batch queries.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Google Maps API key |
| locations | string | yes | Pipe-separated "lat,lng" pairs (e.g., "39.7391,-104.9847|36.4555,-116.8666") |
No output schema declared.
No examples provided.
maps_geocode ~128
"Geocode [address] via Google Maps" / "Google Maps coordinates of [place]" / "lat lng for [address] using Google" — convert an address to lat/lng + formatted address via Google Maps Platform. Premium-quality geocoding (highest accuracy for US addresses); requires Google Maps API key. Use when Mapbox/MapTiler/OpenStreetMap miss the address.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Google Maps API key |
| address | string | yes | Address to geocode (e.g., "1600 Amphitheatre Parkway, Mountain View, CA") |
No output schema declared.
No examples provided.
maps_place_details ~101
"Hours / phone / reviews of [business]" / "Google business info for [place]" / "is [restaurant] open" — full details for a Google Place: address, phone, hours, website, ratings, user reviews. Requires a place ID from `maps_place_search`. Use after search to drill into one specific business.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Google Maps API key |
| place_id | string | yes | Google Place ID |
No output schema declared.
No examples provided.
maps_place_search ~166
"Find restaurants / hotels / coffee shops / [businesses] near [location]" / "nearby [type] within [radius]" / "places to eat in [area]" — find nearby businesses and points of interest via Google Maps Places. Returns names, addresses, Google ratings, distances. Premium-quality POI data; requires Google Maps API key. Use over Yelp/OSM when you want Google's POI coverage and ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Google Maps API key |
| location | string | – | Center point as "lat,lng" (optional) |
| query | string | yes | Search query (e.g., "pizza near Times Square") |
| radius | number | – | Search radius in meters (max 50000, default 5000) |
No output schema declared.
No examples provided.
maps_reverse_geocode ~93
"Reverse geocode [lat,lng] via Google Maps" / "what address is at [coords] in Google" — coordinates → address via Google Maps Platform. Requires Google Maps API key. Use when you need Google's street-address parsing (most accurate for US).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Google Maps API key |
| lat | number | yes | Latitude |
| lng | number | yes | Longitude |
No output schema declared.
No examples provided.
How do I install the Google_maps MCP server?
Google_maps runs locally as an npm package, launched with npx -y @pipeworx/mcp-google_maps. 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-google_maps
claude mcp add pipeworx-io-google-maps -- npx -y @pipeworx/mcp-google_maps
What is the Google_maps MCP server?
Google_maps is an MCP server listed in the public MCP registry as io.github.pipeworx-io/google_maps. Google Maps MCP Pack, geocoding, places, directions, distance matrix, elevation. Uses Google Maps… This page covers its npm package (@pipeworx/mcp-google_maps).
Is the Google_maps MCP server safe to use?
Google_maps scores 83 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 Google_maps MCP server expose?
Google_maps exposes 7 tools: maps_geocode, maps_reverse_geocode, maps_place_search, maps_place_details, maps_directions, and 2 more. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.
Is the Google_maps MCP server still maintained?
Google_maps 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 Google_maps MCP server under?
Google_maps declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.