Is Multi Gmail MCP safe to use?

Multi Gmail MCP has an HVTrust score of 42.3/100 (Grade D), ranked #1118 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Multi Gmail MCP?

Multi Gmail MCP scores 42.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 19 GitHub stars and is categorized under MCP Servers.

Multi Gmail MCP

gx-55/multi-gmail-mcp

MCP Servers JavaScript Listed MIT

Is Multi Gmail MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.9 / 10

Provenance None

Signed commits 5%

Last push 44d ago

Compare Multi Gmail MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Multi Gmail MCP scores 42.3/100 (Grade D), ranked #1118 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 2.9/10; 5% of recent commits are signed; last pushed 2026-08-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Multi Gmail MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Multi Gmail MCP’s 42.3.

Where the 42.3 comes from

HVTrust dimensions vs the MCP Servers average

42.3 / 100 · 100.0% confidence

Multi Gmail MCP MCP Servers average (775 agents)

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

3.9 / 25

6.4 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

11.0 / 17

1.2 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.1 / 20

3.0 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.5 / 20

1.7 below 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 77 spots (#1194 → #1117)

2026-09-23

HVTrust Changed

HVTrust up 22.8pts (19.5 → 42.3)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.9/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.

Refresh maintenance signals The repo was last pushed 44 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Multi Gmail MCP View MCP Servers Report missing data

32.0

Activity sub-score · out of 100

#659

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

Forks

Last Push

2026-08-13

44 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲9

was #1127

Analysis

Activity Inputs

32.0 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

18.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.9 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 1

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Multi Gmail MCP

Public trust evidence for Multi Gmail MCP 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 Multi Gmail MCP publish package provenance?

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

Multi Gmail MCP has an OpenSSF Scorecard score of 2.9/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 Multi Gmail MCP actively maintained?

Slowing down. Last push was 44 days ago — keep an eye on whether activity resumes.

What license does Multi Gmail MCP use?

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

Are Multi Gmail MCP's commits signed?

4% of the last 100 commits to Multi Gmail 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

Multi Gmail MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

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

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

low confidence

Unknown

Package source metadata is missing or inconclusive

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 Multi Gmail 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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-13

Activity Resumed

Activity resumed

Maintain Multi Gmail MCP?

For maintainers

HVTrust scores Multi Gmail 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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 77 spots (#1194 → #1117)

2026-09-23

HVTrust Changed

HVTrust up 22.8pts (19.5 → 42.3)

2026-09-22

Newly Listed

First tracked at rank #1194

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 59 spots (#1047 → #1106)

2026-09-12

Activity Score Changed

Activity score down 6pts (40 → 33)

2026-09-11

Rank Moved

Rank dropped 16 spots (#1031 → #1047)

2026-09-09

Rank Moved

Rank dropped 17 spots (#1013 → #1030)

2026-09-07

Rank Moved

Rank dropped 41 spots (#965 → #1006)

2026-09-06

Rank Moved

Rank dropped 14 spots (#951 → #965)

2026-09-05

Rank Moved

Rank dropped 46 spots (#905 → #951)

2026-09-04

Rank Moved

Rank dropped 30 spots (#875 → #905)

2026-09-03

Rank Moved

Rank dropped 58 spots (#817 → #875)

2026-09-02

Rank Moved

Rank rose 317 spots (#1134 → #817)

2026-09-02

HVTrust Changed

HVTrust up 16.6pts (29.4 → 46.0)

2026-09-01

Rank Moved

Rank dropped 43 spots (#1091 → #1134)

2026-08-31

Rank Moved

Rank dropped 28 spots (#1063 → #1091)

2026-08-30

Scorecard Added

OSSF Scorecard: 2.9/10

2026-08-30

Rank Moved

Rank rose 218 spots (#1281 → #1063)

2026-08-30

HVTrust Changed

HVTrust up 13.4pts (16.1 → 29.5)

2026-08-26

Rank Moved

Rank dropped 20 spots (#1240 → #1260)

2026-08-16

Rank Moved

Rank dropped 31 spots (#1204 → #1235)

2026-08-13

Activity Resumed

Activity resumed

2026-08-13

Rank Moved

Rank rose 63 spots (#1269 → #1206)

2026-08-13

HVTrust Changed

HVTrust up 3.5pts (13.0 → 16.5)

2026-08-13

Activity Score Changed

Activity score up 20pts (22 → 43)

2026-08-10

Rank Moved

Rank dropped 79 spots (#1189 → #1268)

2026-08-08

Newly Listed

First tracked at rank #1188

GitHub → npm: multi-gmail-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/multi-gmail-mcp.svg)](https://hvtracker.net/agents/multi-gmail-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/multi-gmail-mcp"><img src="https://hvtracker.net/badge/multi-gmail-mcp.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