Is Google Workspace MCP safe to use?

Google Workspace MCP has an HVTrust score of 64.0/100 (Grade C), ranked #234 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Google Workspace MCP?

Google Workspace MCP scores 64.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.0k GitHub stars and is categorized under MCP Servers.

Google Workspace MCP

taylorwilsdon/google_workspace_mcp

Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google

MCP Servers Python Grade C Listed MIT

64.0/100

Rank #234 of 1204

Compare Google Workspace MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Rank +2

Is Google Workspace MCP safe? Google Workspace MCP scores 64.0/100 (Grade C), ranked #234 of 1204 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.4/10; 26% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#66 CN Scraper MCP — 64.3 (C) → #67 CrowdSentinels AI MCP — 64.1 (C) → #69 Cronometer Api MCP — 63.9 (C) → #70 Brandsystem MCP — Brand Guidelines for AI — 63.9 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 53 spots (#180 → #233)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.4/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 Workspace MCP View MCP Servers Report missing data

84.7

Activity sub-score · out of 100

#68

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 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 →

Activity & Reach

Stars

3.0k

Forks

933

Last Push

2026-08-09

today

Commits (4 wk)

127

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #233

Analysis

HVTrust Dimensions vs MCP Servers

64.0 / 100 · 100.0% confidence

Google Workspace MCP MCP Servers average (718 agents)

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

9.3 / 25

4.2 above avg 5.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

13.9 / 17

5.1 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.5 above avg 12.5

AdoptionLog-scaled stars · package downloads

8.3 / 20

2.8 above avg 5.5

Activity Inputs

84.7 / 100

StarsRepository reach

20.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

13.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.4 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

26%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 8

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 4

Security-Policy 10

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 6

Is Google Workspace MCP safe?

Google Workspace MCP 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 Workspace MCP publish package provenance?

No published build provenance is currently detected for Google Workspace MCP. 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 Workspace MCP have an OpenSSF Scorecard?

Google Workspace MCP has an OpenSSF Scorecard score of 6.4/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 Workspace MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Google Workspace MCP use?

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

Are Google Workspace MCP's commits signed?

26% of the last 100 commits to Google Workspace MCP 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 Workspace MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 Workspace MCP'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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintain Google Workspace MCP?

For maintainers

HVTrust scores Google Workspace MCP 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-08-08

Rank Moved

Rank dropped 53 spots (#180 → #233)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-07-23

Rank Moved

Rank rose 25 spots (#205 → #180)

2026-07-20

Rank Moved

Rank dropped 18 spots (#183 → #201)

2026-07-15

Scorecard Added

OSSF Scorecard: 6.7/10

2026-07-15

Grade Changed

Trust grade D → C

2026-07-15

Rank Moved

Rank rose 210 spots (#389 → #179)

2026-07-15

HVTrust Changed

HVTrust up 38.0pts (24.4 → 62.4)

2026-07-14

Newly Listed

First tracked at rank #389

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/google-workspace-mcp.svg)](https://hvtracker.net/agents/google-workspace-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/google-workspace-mcp"><img src="https://hvtracker.net/badge/google-workspace-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON