Is Google Health Fitbit MCP safe to use?

Google Health Fitbit MCP has an HVTrust score of 43.8/100 (Grade D), ranked #1091 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 Fitbit MCP?

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

Google Health Fitbit MCP

BerkKilicoglu/google-health-fitbit-mcp

Connect your Fitbit / Pixel Watch data to any AI assistant via MCP. Read-only MCP server for the Google Health API. Your health data → any AI assistant, tokens never leave your machine.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 2.1 / 10

Provenance None

Signed commits 0%

Last push 53d ago

Compare Google Health Fitbit MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Google Health Fitbit MCP scores 43.8/100 (Grade D), ranked #1091 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.1/10; recent commits are unsigned; last pushed 2026-08-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google Health Fitbit MCP compares in MCP Servers

#637 Deployhq MCP Server 43.9 +0.1
#638 MCP Mermaid 43.8 ±0
#639 Google Health Fitbit MCP 43.8 this agent
#640 Kolada MCP Server 43.6 −0.2
#641 MCP Victorialogs 43.6 −0.2

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

Where the 43.8 comes from

HVTrust dimensions vs the MCP Servers average

43.8 / 100 · 100.0% confidence

Google Health Fitbit MCP MCP Servers average (775 agents)

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

2.6 / 25

7.7 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

10.3 / 17

1.9 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

8.5 / 20

3.6 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.6 / 20

1.6 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 134 spots (#1218 → #1084)

2026-09-23

HVTrust Changed

HVTrust up 26.0pts (17.9 → 43.9)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.1/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 53 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Google Health Fitbit MCP View MCP Servers Report missing data

27.4

Activity sub-score · out of 100

#639

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

53 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #1094

Analysis

Activity Inputs

27.4 / 100

StarsRepository reach

7.4 / 30

FreshnessLast push recency

17.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.1 / 10

OpenSSF Scorecard · scanned Sep 25, 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 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 9

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Common questions about Google Health Fitbit MCP

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

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

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

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

What license does Google Health Fitbit MCP use?

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

Are Google Health Fitbit MCP's commits signed?

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

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain Google Health Fitbit MCP?

For maintainers

HVTrust scores Google Health Fitbit 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 134 spots (#1218 → #1084)

2026-09-23

HVTrust Changed

HVTrust up 26.0pts (17.9 → 43.9)

2026-09-22

Newly Listed

First tracked at rank #1218

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 12 spots (#1055 → #1067)

2026-09-11

Rank Moved

Rank dropped 11 spots (#1044 → #1055)

2026-09-09

Rank Moved

Rank dropped 18 spots (#1027 → #1045)

2026-09-08

Rank Moved

Rank dropped 12 spots (#1015 → #1027)

2026-09-07

Rank Moved

Rank dropped 34 spots (#981 → #1015)

2026-09-06

Rank Moved

Rank dropped 16 spots (#965 → #981)

2026-09-05

Rank Moved

Rank rose 252 spots (#1217 → #965)

2026-09-05

HVTrust Changed

HVTrust up 14.8pts (30.4 → 45.2)

2026-09-04

Rank Moved

Rank dropped 18 spots (#1199 → #1217)

2026-09-03

Rank Moved

Rank dropped 52 spots (#1147 → #1199)

2026-09-02

Rank Moved

Rank dropped 388 spots (#759 → #1147)

2026-09-02

HVTrust Changed

HVTrust down 15.3pts (46.6 → 31.3)

2026-09-01

Rank Moved

Rank dropped 31 spots (#728 → #759)

2026-08-31

Rank Moved

Rank rose 305 spots (#1033 → #728)

2026-08-31

HVTrust Changed

HVTrust up 15.2pts (31.5 → 46.7)

2026-08-30

Rank Moved

Rank dropped 366 spots (#667 → #1033)

2026-08-30

HVTrust Changed

HVTrust down 15.4pts (46.9 → 31.5)

2026-08-29

Rank Moved

Rank dropped 45 spots (#622 → #667)

2026-08-28

Rank Moved

Rank dropped 21 spots (#601 → #622)

2026-08-27

Rank Moved

Rank dropped 11 spots (#590 → #601)

2026-08-26

Scorecard Added

OSSF Scorecard: 2.1/10

2026-08-26

Rank Moved

Rank rose 175 spots (#765 → #590)

2026-08-26

HVTrust Changed

HVTrust up 15.7pts (31.3 → 47.0)

2026-08-24

Rank Moved

Rank rose 310 spots (#1072 → #762)

2026-08-24

HVTrust Changed

HVTrust up 11.3pts (20.1 → 31.4)

2026-08-22

Rank Moved

Rank dropped 307 spots (#761 → #1068)

2026-08-22

HVTrust Changed

HVTrust down 11.3pts (31.5 → 20.2)

2026-08-19

Rank Moved

Rank rose 309 spots (#1071 → #762)

2026-08-19

HVTrust Changed

HVTrust up 11.3pts (20.2 → 31.5)

2026-08-17

Rank Moved

Rank dropped 310 spots (#760 → #1070)

2026-08-17

HVTrust Changed

HVTrust down 11.5pts (31.7 → 20.2)

2026-08-16

Rank Moved

Rank dropped 14 spots (#746 → #760)

2026-08-13

Rank Moved

Rank rose 286 spots (#1029 → #743)

2026-08-13

HVTrust Changed

HVTrust up 11.3pts (20.6 → 31.9)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank dropped 270 spots (#759 → #1029)

2026-08-12

HVTrust Changed

HVTrust down 10.2pts (30.8 → 20.6)

2026-08-10

Rank Moved

Rank dropped 40 spots (#719 → #759)

2026-08-08

Newly Listed

First tracked at rank #713

GitHub → npm: google-health-fitbit-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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