Is Google Maps MCP Server safe to use?

Google Maps MCP Server has an HVTrust score of 64.2/100 (Grade C), ranked #502 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Google Maps MCP Server?

Google Maps MCP Server scores 64.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 463 GitHub stars and is categorized under MCP Servers.

Google Maps MCP Server

cablate/mcp-google-map

A powerful Model Context Protocol (MCP) server providing comprehensive Google Maps API integration with LLM processing capabilities.

MCP Servers TypeScript Listed MIT

Is Google Maps MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.6 / 10

Provenance None

Signed commits 49%

Last push 10d ago

Compare Google Maps MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Google Maps MCP Server scores 64.2/100 (Grade C), ranked #502 of 1325 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.6/10; 49% of recent commits are signed; last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google Maps MCP Server compares in MCP Servers

#289 Computer Use 64.2 ±0
#290 CrowdSentinels AI MCP 64.2 ±0
#291 Google Maps MCP Server 64.2 this agent
#292 GitLab MCP Server 64.1 −0.1
#293 Domain Search MCP 64.1 −0.1

Bars show each HVTrust score; the tick marks Google Maps MCP Server’s 64.2.

Where the 64.2 comes from

HVTrust dimensions vs the MCP Servers average

64.2 / 100 · 100.0% confidence

Google Maps MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.2 / 25

2.1 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.4 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.3 / 20

5.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

10.5 / 20

3.3 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-26

Rank Moved

Rank dropped 16 spots (#486 → #502)

2026-09-24

Rank Moved

Rank rose 11 spots (#492 → #481)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Google Maps MCP Server View MCP Servers Report missing data

67.5

Activity sub-score · out of 100

#291

In MCP Servers

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

2026-08-11 2026-09-26

Activity & Reach

Stars

463

Forks

Last Push

2026-09-16

10 days ago

Commits (4 wk)

Downloads (7d)

1,119

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼16

was #486

Analysis

Activity Inputs

67.5 / 100

StarsRepository reach

16.0 / 30

FreshnessLast push recency

23.6 / 25

ActivityRecent commits

18.6 / 25

CommunityFork signal

9.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.6 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

49%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Google Maps MCP Server

Google Maps MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Google Maps MCP Server publish package provenance?

No published build provenance is currently detected for Google Maps MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Google Maps MCP Server have an OpenSSF Scorecard?

Google Maps MCP Server has an OpenSSF Scorecard score of 4.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Google Maps MCP Server actively maintained?

Maintained. Last push was 10 days ago.

What license does Google Maps MCP Server use?

Google Maps MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Google Maps MCP Server's commits signed?

49% of the last 100 commits to Google Maps MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

high confidence

Implemented

Google Maps MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

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.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-26

Rank Moved

Rank dropped 16 spots (#486 → #502)

2026-09-24

Rank Moved

Rank rose 11 spots (#492 → #481)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 276 spots (#768 → #492)

2026-09-23

HVTrust Changed

HVTrust up 34.6pts (29.7 → 64.3)

2026-09-22

Newly Listed

First tracked at rank #768

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank rose 95 spots (#563 → #468)

2026-09-17

HVTrust Changed

HVTrust up 3.0pts (61.7 → 64.7)

2026-09-16

Rank Moved

Rank rose 53 spots (#616 → #563)

2026-09-16

Activity Score Changed

Activity score up 8pts (61 → 69)

2026-09-15

Rank Moved

Rank dropped 13 spots (#603 → #616)

2026-09-12

Rank Moved

Rank dropped 59 spots (#541 → #600)

2026-09-11

Rank Moved

Rank rose 83 spots (#624 → #541)

2026-09-11

HVTrust Changed

HVTrust up 3.0pts (59.0 → 62.0)

2026-09-11

Activity Score Changed

Activity score up 8pts (55 → 63)

2026-09-08

Rank Moved

Rank dropped 10 spots (#601 → #611)

2026-09-07

Rank Moved

Rank dropped 46 spots (#555 → #601)

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 533 spots (#1081 → #548)

2026-09-05

HVTrust Changed

HVTrust up 20.8pts (38.7 → 59.5)

2026-09-04

Rank Moved

Rank dropped 24 spots (#1057 → #1081)

2026-09-03

Rank Moved

Rank dropped 54 spots (#1003 → #1057)

2026-09-02

Grade Changed

Trust grade C → D

2026-09-02

Rank Moved

Rank dropped 581 spots (#422 → #1003)

2026-09-02

HVTrust Changed

HVTrust down 20.9pts (59.7 → 38.8)

2026-09-01

Rank Moved

Rank dropped 11 spots (#411 → #422)

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 475 spots (#886 → #411)

2026-08-31

HVTrust Changed

HVTrust up 20.9pts (38.9 → 59.8)

2026-08-30

Grade Changed

Trust grade C → D

2026-08-30

Rank Moved

Rank dropped 494 spots (#392 → #886)

2026-08-30

HVTrust Changed

HVTrust down 21.0pts (59.9 → 38.9)

2026-08-29

Scorecard Added

OSSF Scorecard: 4.3/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 470 spots (#862 → #392)

2026-08-29

HVTrust Changed

HVTrust up 24.2pts (35.7 → 59.9)

2026-08-28

Rank Moved

Rank dropped 29 spots (#833 → #862)

2026-08-27

Rank Moved

Rank dropped 24 spots (#809 → #833)

2026-08-26

Rank Moved

Rank dropped 105 spots (#704 → #809)

2026-08-24

Rank Moved

Rank rose 305 spots (#1009 → #704)

2026-08-24

HVTrust Changed

HVTrust up 14.5pts (21.4 → 35.9)

2026-08-22

Rank Moved

Rank dropped 306 spots (#706 → #1012)

2026-08-22

HVTrust Changed

HVTrust down 14.0pts (35.4 → 21.4)

2026-08-18

Rank Moved

Rank rose 295 spots (#1006 → #711)

2026-08-18

HVTrust Changed

HVTrust up 13.8pts (21.5 → 35.3)

2026-08-17

Rank Moved

Rank dropped 296 spots (#710 → #1006)

2026-08-17

HVTrust Changed

HVTrust down 13.8pts (35.3 → 21.5)

2026-08-13

Rank Moved

Rank rose 358 spots (#1062 → #704)

2026-08-13

HVTrust Changed

HVTrust up 14.8pts (20.0 → 34.8)

2026-08-13

Activity Score Changed

Activity score up 11pts (45 → 56)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank dropped 325 spots (#737 → #1062)

2026-08-12

HVTrust Changed

HVTrust down 12.3pts (32.3 → 20.0)

2026-08-10

Rank Moved

Rank dropped 39 spots (#696 → #735)

2026-08-08

Newly Listed

First tracked at rank #996

GitHub → npm: @cablate/mcp-google-map

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/google-maps-mcp-server.svg)](https://hvtracker.net/agents/google-maps-mcp-server)
            
HTML:
            <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

Data sources
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.3 · Raw JSON