Is Google Health MCP safe to use?

Google Health MCP has an HVTrust score of 53.9/100 (Grade C), ranked #827 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 Health MCP?

Google Health MCP scores 53.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 62 GitHub stars and is categorized under MCP Servers.

Google Health MCP

davidmosiah/google-health-mcp

Local-first MCP server for Google Health API v4 (Fitbit + Pixel Watch) — Claude/Cursor/Hermes

MCP Servers TypeScript Listed MIT

Is Google Health MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.4 / 10

Provenance None

Signed commits 6%

Last push 28d ago

Compare Google Health MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Google Health MCP scores 53.9/100 (Grade C), ranked #827 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.4/10; 6% of recent commits are signed; last pushed 2026-08-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google Health MCP compares in MCP Servers

#464 tdmcp — TouchDesigner MCP server 53.9 ±0
#465 SeedanceMCP 53.9 ±0
#466 Google Health MCP 53.9 this agent
#467 Plumb MCP 53.9 ±0
#468 Doom MCP 53.9 ±0

Bars show each HVTrust score; the tick marks Google Health MCP’s 53.9.

Where the 53.9 comes from

HVTrust dimensions vs the MCP Servers average

53.9 / 100 · 100.0% confidence

Google Health MCP MCP Servers average (775 agents)

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

5.8 / 25

4.5 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.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.3 / 20

0.7 below avg 12.0

AdoptionLog-scaled stars · package downloads

7.8 / 20

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

Rank Moved

Rank dropped 28 spots (#794 → #822)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.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 Health MCP View MCP Servers Report missing data

40.4

Activity sub-score · out of 100

#466

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

Forks

Last Push

2026-08-29

28 days ago

Commits (4 wk)

Downloads (7d)

396

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼5

was #822

Analysis

Activity Inputs

40.4 / 100

StarsRepository reach

10.8 / 30

FreshnessLast push recency

21.1 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

4.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 1

Common questions about Google Health MCP

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

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

Google Health MCP has an OpenSSF Scorecard score of 4.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 Health MCP actively maintained?

Maintained. Last push was 28 days ago.

What license does Google Health MCP use?

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

Are Google Health MCP's commits signed?

5% of the last 100 commits to Google Health 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 Health 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

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

Maintain Google Health MCP?

For maintainers

HVTrust scores Google Health 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-25

Rank Moved

Rank dropped 28 spots (#794 → #822)

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 230 spots (#1023 → #793)

2026-09-23

HVTrust Changed

HVTrust up 30.3pts (24.4 → 54.7)

2026-09-22

Newly Listed

First tracked at rank #1023

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank rose 17 spots (#789 → #772)

2026-09-17

Rank Moved

Rank dropped 13 spots (#776 → #789)

2026-09-14

Rank Moved

Rank dropped 41 spots (#723 → #764)

2026-09-13

Rank Moved

Rank dropped 10 spots (#713 → #723)

2026-09-12

Rank Moved

Rank dropped 23 spots (#690 → #713)

2026-09-11

Rank Moved

Rank dropped 21 spots (#669 → #690)

2026-09-10

Rank Moved

Rank dropped 20 spots (#649 → #669)

2026-09-08

Rank Moved

Rank dropped 13 spots (#629 → #642)

2026-09-07

Rank Moved

Rank dropped 66 spots (#563 → #629)

2026-09-05

Rank Moved

Rank dropped 77 spots (#478 → #555)

2026-09-04

Rank Moved

Rank dropped 15 spots (#463 → #478)

2026-09-03

Rank Moved

Rank dropped 50 spots (#413 → #463)

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 513 spots (#926 → #413)

2026-09-02

HVTrust Changed

HVTrust up 20.7pts (40.0 → 60.7)

2026-09-01

Rank Moved

Rank dropped 37 spots (#889 → #926)

2026-08-31

Rank Moved

Rank dropped 35 spots (#854 → #889)

2026-08-30

Scorecard Added

OSSF Scorecard: 5.1/10

2026-08-30

Rank Moved

Rank rose 272 spots (#1126 → #854)

2026-08-30

HVTrust Changed

HVTrust up 17.9pts (22.4 → 40.3)

2026-08-29

Rank Moved

Rank dropped 35 spots (#1091 → #1126)

2026-08-28

Rank Moved

Rank dropped 29 spots (#1062 → #1091)

2026-08-27

Rank Moved

Rank dropped 21 spots (#1041 → #1062)

2026-08-26

Rank Moved

Rank dropped 66 spots (#975 → #1041)

2026-08-24

Rank Moved

Rank dropped 13 spots (#961 → #974)

2026-08-22

Rank Moved

Rank rose 11 spots (#971 → #960)

2026-08-17

Rank Moved

Rank rose 11 spots (#975 → #964)

2026-08-16

Rank Moved

Rank dropped 27 spots (#948 → #975)

2026-08-13

Rank Moved

Rank dropped 11 spots (#943 → #954)

2026-08-12

Rank Moved

Rank rose 14 spots (#957 → #943)

2026-08-10

Rank Moved

Rank dropped 57 spots (#902 → #959)

2026-08-08

Newly Listed

First tracked at rank #893

GitHub → npm: google-health-mcp-unofficial

Embed Badge Badge guide for maintainers →

For maintainers

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