updated 2026-10-16 20:06 UTC

Google Health MCP

Repository Website

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? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.8 / 10
Provenance None
Signed commits 8%
Last push 8d ago
Advisories None known
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 59.0/100 (Grade C), ranked #702 of 1378 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 5.8/10; 8% of recent commits are signed; no published advisory affects its latest release (google-health-mcp-unofficial); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google Health MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Google Health MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/davidmosiah/google-health-mcp, MIT, last pushed 2026-10-08. 8% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.8/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    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 10
    Security-Policy 4
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: google-health-mcp-unofficial 0.7.8. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 5.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Google Health MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Google Health MCP compares in MCP Servers

  1. #378 Glade MCP 59.5 +0.5
  2. #379 Microsoft Learn MCP 59.2 +0.2
  3. #380 Google Health MCP 59.0 this agent
  4. #381 MCP Devkit Server 59.0 ±0
  5. #382 Pyslang MCP 59.0 ±0

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

Where the 59.0 comes from

HVTrust dimensions vs the MCP Servers average

59.0 / 100 · 100.0% confidence

Google Health MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.6 / 25
2.9 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
1.1 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.4 / 20
1.1 above avg 12.3
AdoptionLog-scaled stars · package downloads
7.8 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Rank Moved
Rank rose 25 spots (#727 → #702)
2026-10-12
Rank Moved
Rank dropped 10 spots (#701 → #711)
2026-10-11
Rank Moved
Rank rose 100 spots (#801 → #701)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/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
46.0
Activity sub-score · out of 100
#380
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 →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed 8 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
70
Forks
11
Last Push
2026-10-08
8 days ago
Commits (4 wk)
2
Downloads (7d)
342
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▲25
was #727

Analysis

Activity Inputs

46.0 / 100
StarsRepository reach
11.1 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
5.0 / 20

Common questions about Google Health MCP

Google Health 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 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 5.8/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 8 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?
8% 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
Rank 37HVTrust 4Listed 2Grade 2Score 2Scorecard 1Delisted 1MCP 1
2026-10-16
Rank Moved
Rank rose 25 spots (#727 → #702)
2026-10-12
Rank Moved
Rank dropped 10 spots (#701 → #711)
2026-10-11
Rank Moved
Rank rose 100 spots (#801 → #701)
2026-10-11
HVTrust Changed
HVTrust up 3.0pts (55.4 → 58.4)
2026-10-09
Rank Moved
Rank dropped 10 spots (#788 → #798)
2026-10-08
Rank Moved
Rank rose 32 spots (#820 → #788)
2026-10-08
Activity Score Changed
Activity score up 6pts (41 → 47)
2026-10-07
Rank Moved
Rank rose 72 spots (#892 → #820)
2026-10-07
Activity Score Changed
Activity score up 5pts (35 → 41)
2026-10-01
Rank Moved
Rank dropped 10 spots (#877 → #887)
2026-09-28
Rank Moved
Rank dropped 36 spots (#827 → #863)
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 → Website → npm: google-health-mcp-unofficial

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 59.0 Grade C
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.4 · Raw JSON