updated 2026-08-12 05:02 UTC

Google Maps MCP Server

cablate/mcp-google-map

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

MCP Servers TypeScript Grade D Listed MIT
32.3/100
Rank #735 of 1283
Compare Google Maps MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-08 · 35d ago
Recent change
Rank +1

Is Google Maps MCP Server safe? Google Maps MCP Server scores 32.3/100 (Grade D), ranked #735 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 46% of recent commits are signed; last pushed 2026-07-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#331 Doom MCP — 32.5 (D) → #332 Codex MCP Tool — 32.5 (D) → #334 shadcn-ui MCP Server — 32.1 (D) → #335 One Search MCP — 32.1 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 39 spots (#696 → #735)
2026-08-08
Newly Listed
First tracked at rank #996
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
Refresh maintenance signals The repo was last pushed 35 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Google Maps MCP Server View MCP Servers Report missing data
44.8
Activity sub-score · out of 100
#333
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 35 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
421
Forks
80
Last Push
2026-07-08
35 days ago
Commits (4 wk)
0
Downloads (7d)
661
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲2
was #737

Analysis

HVTrust Dimensions vs MCP Servers

32.3 / 100 · 67.0% confidence

Google Maps MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.3 / 25
2.7 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
9.7 / 20
2.7 below avg 12.4
AdoptionLog-scaled stars · package downloads
10.1 / 20
4.3 above avg 5.8

Activity Inputs

44.8 / 100
StarsRepository reach
15.8 / 30
FreshnessLast push recency
20.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
46%
of last 100 commits verified

Is Google Maps MCP Server safe?

Public trust evidence for Google Maps MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for Google Maps MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Google Maps MCP Server actively maintained?
Slowing down. Last push was 35 days ago — keep an eye on whether activity resumes.
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?
46% 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
medium confidence
Declared
Declared plugin/integration 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

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
Listed 1Rank 1
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
HVTrust 32.3 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON