Google Maps MCP Server
18 Google Maps tools and 3 Agent Skills for place search, routes, travel planning, and local SEO—via MCP or standalone CLI.
Is Google Maps MCP Server safe? Promising trust profile, but some evidence still deserves review.
Compare Google Maps MCP Server
How does it stack up against its MCP Servers neighbours?
- RU Marketplace MCP same score
- Nse Bse Indian Stock Market Data MCP same score
- Crabeye MCP Bridge same score
In detail: Google Maps MCP Server scores 57.9/100 (Grade C), ranked #761 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 50% of recent commits are signed; no published advisory affects its latest release (@cablate/mcp-google-map); last pushed 2026-10-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How Google Maps MCP Server could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.6 → 72.5 B · #188 of 778
- Raise the OSSF Scorecard from 4.2 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dependency-Update-Tool 0 +10.0 → 67.9 B · #251 of 778
- Sign every commit50% signed today +2.4 → 60.3 C · #378 of 778
Chain of custody
Scanners check what the code says. This traces who ships Google Maps MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/cablate/mcp-google-map, MIT, last pushed 2026-10-22. 50% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 2SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages Linked, not attested
- npm @cablate/mcp-google-map Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: @cablate/mcp-google-map 0.0.69. No published advisory affects it (OSV, checked 2026-11-09).
Changes to this chain
- 2026-08-29 OSSF Scorecard: 4.3/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Google Maps MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Google Maps MCP Server compares in MCP Servers
- #411 RU Marketplace MCP 57.9 ±0
- #412 Nse Bse Indian Stock Market Data MCP 57.9 ±0
- #413 Google Maps MCP Server 57.9 this agent
- #414 Crabeye MCP Bridge 57.9 ±0
- #415 MCPfinder - MCP Server Discovery 57.9 ±0
Bars show each HVTrust score; the tick marks Google Maps MCP Server’s 57.9.
Where the 57.9 comes from
HVTrust dimensions vs the MCP Servers average
57.9 / 100 · 100.0% confidenceGoogle Maps MCP Server MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
51.7 / 100Common questions about Google Maps MCP Server
Does Google Maps MCP Server publish package provenance?
Does Google Maps MCP Server have an OpenSSF Scorecard?
Is Google Maps MCP Server actively maintained?
What license does Google Maps MCP Server use?
Are Google Maps MCP Server's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Google Maps MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Google Maps MCP Server?
For maintainers
HVTrust scores Google Maps MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/google-maps-mcp-server)
<a href="https://hvtracker.net/agents/google-maps-mcp-server"><img src="https://hvtracker.net/badge/google-maps-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON