Google Maps (apurvaumredkar) MCP Server
mcp-server-google-maps
npm
v1.0.4
Published by apurvaumredkar — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP Server for Google Maps — 15 tools covering Places, Routes, Static Maps, Street View, Geocoding, Timezone, Address Validation and more.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Hardcoded egress to an external endpoint (dist/maps-client.js)MTC-SRC-003
In the server's implementation (`dist/maps-client.js:115`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const res = await fetch(`https://places.googleapis.com/v1/${photo.name}/media?${qs}`, { headers: { 'X-Goog-Api-Key
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/maps-client.js
Tools 15
Each tool and what it can reach — statically extracted from the published source.
maps_elevationno sensitive capabilitymaps_embed_urlno sensitive capabilitymaps_static_mapno sensitive capabilitymaps_street_viewno sensitive capabilityplaces_address_validationno sensitive capabilityplaces_autocompleteno sensitive capabilityplaces_detailsno sensitive capabilityplaces_geocodeno sensitive capabilityplaces_nearby_searchno sensitive capabilityplaces_photosno sensitive capability
Show 5 more tools ↓
places_text_searchno sensitive capabilityplaces_timezoneno sensitive capabilityroutes_computeno sensitive capabilityroutes_matrixno sensitive capabilityroutes_optimizeno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.4 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-server-google-maps --onlineOther implementations of Google Maps 7
Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →
The official Google Maps server: geocoding, places and directions data for assistants.
Model Context Protocol server for Google Maps Platform APIs - provides geocoding, places search, routing, and geospatial tools
Google Maps MCP Pack — geocoding, places, directions, distance matrix, elevation.
Google Maps MCP server using Google Places API.
Production-ready MCP server for Google Maps Platform APIs - Directions, Places, Geocoding, Roads, and Distance Matrix
MCP Google Maps server
More in Lifestyle & Local
MCP server for Australian address search and validation via Addressr
Admissions data & match scores for law, medical, dental, MBA, pharmacy, vet, optometry schools
Live AI data for agents: model releases, regulations (EU AI Act), GenAI glossary, daily news.
AirTreks MCP Server — complex flight routing intelligence for AI agents. Plan multi-city trips, validate alliance routings, get carrier recommendations, and create trip ideas.
Physician-reviewed medical opinions and prescriptions for AI agents.
Thin MCP server + CLI that proxy the atrium /api/v1 observability surface using an oc_live_ Bearer key. Talks HTTP only — no Convex imports.