Is Withings Health Data safe to use?

Withings Health Data has an HVTrust score of 42.7/100 (Grade D), ranked #1161 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Withings Health Data?

Withings Health Data scores 42.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 45 GitHub stars and is categorized under MCP Servers.

Withings Health Data

Repository

Website by akutishevsky

MCP server for Withings health data integration

MCP Servers TypeScript Listed MIT

Is Withings Health Data safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.5 / 10

Provenance None

Signed commits 32%

Last push 62d ago

Compare Withings Health Data

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Withings Health Data scores 42.7/100 (Grade D), ranked #1161 of 1374 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 4.5/10; 32% of recent commits are signed; last pushed 2026-09-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Withings Health Data 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.

Raise the OSSF Scorecard from 4.5 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +9.4 → 52.1 C · #533 of 778
Sign every commit32% signed today +3.4 → 46.1 D · #627 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Partly signed

github.com/akutishevsky/withings-mcp, MIT, last pushed 2026-09-09. 32% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies10
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 7

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 10

SAST 10

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. Withings Health Data is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-26 OSSF Scorecard: 4.6/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Withings Health Data’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 Withings Health Data compares in MCP Servers

#663 SocialGPT 42.8 +0.1
#664 N8n MCP 42.8 +0.1
#665 Withings Health Data 42.7 this agent
#666 Perplexity Comet MCP 42.7 ±0
#667 MCP Trino 42.6 −0.1

Bars show each HVTrust score; the tick marks Withings Health Data’s 42.7.

Where the 42.7 comes from

HVTrust dimensions vs the MCP Servers average

42.7 / 100 · 100.0% confidence

Withings Health Data MCP Servers average (778 agents)

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

7.2 / 25

3.6 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

7.9 / 20

4.3 below avg 12.2

AdoptionLog-scaled stars · package downloads

4.0 / 20

3.6 below avg 7.6

Quick Trust Read

What Would Improve It

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

Maintainer Checklist

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

Compare with another agent View MCP Servers Report missing data

31.7

Activity sub-score · out of 100

#665

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

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-09-09

62 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1162

Analysis

Activity Inputs

31.7 / 100

StarsRepository reach

10.0 / 30

FreshnessLast push recency

16.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.2 / 20

Common questions about Withings Health Data

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

No published build provenance is currently detected for Withings Health Data. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Withings Health Data have an OpenSSF Scorecard?

Withings Health Data has an OpenSSF Scorecard score of 4.5/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 Withings Health Data actively maintained?

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

What license does Withings Health Data use?

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

Are Withings Health Data's commits signed?

32% of the last 100 commits to Withings Health Data 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

Withings Health Data appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

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

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 Withings Health Data'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

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Supabase

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Withings Health Data?

For maintainers

HVTrust scores Withings Health Data 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-10-09

Rank Moved

Rank dropped 73 spots (#1028 → #1101)

2026-10-09

Activity Score Changed

Activity score down 8pts (43 → 36)

2026-09-30

Rank Moved

Rank dropped 11 spots (#992 → #1003)

2026-09-25

Rank Moved

Rank dropped 15 spots (#931 → #946)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Supabase

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 409 spots (#518 → #927)

2026-09-23

HVTrust Changed

HVTrust up 9.8pts (40.0 → 49.8)

2026-09-22

Newly Listed

First tracked at rank #518

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-15

Rank Moved

Rank dropped 11 spots (#894 → #905)

2026-09-12

Rank Moved

Rank dropped 12 spots (#887 → #899)

2026-09-11

Rank Moved

Rank dropped 16 spots (#871 → #887)

2026-09-09

Rank Moved

Rank rose 11 spots (#888 → #877)

2026-09-08

Grade Changed

Trust grade D → C

2026-09-08

Rank Moved

Rank rose 44 spots (#932 → #888)

2026-09-07

Rank Moved

Rank dropped 38 spots (#894 → #932)

2026-09-06

Rank Moved

Rank dropped 16 spots (#878 → #894)

2026-09-05

Rank Moved

Rank dropped 57 spots (#821 → #878)

2026-09-04

Rank Moved

Rank dropped 34 spots (#787 → #821)

2026-09-03

Rank Moved

Rank dropped 44 spots (#743 → #787)

2026-09-02

Rank Moved

Rank dropped 33 spots (#710 → #743)

2026-09-01

Rank Moved

Rank dropped 30 spots (#680 → #710)

2026-08-31

Rank Moved

Rank dropped 41 spots (#639 → #680)

2026-08-30

Rank Moved

Rank rose 87 spots (#726 → #639)

2026-08-30

HVTrust Changed

HVTrust up 4.2pts (44.6 → 48.8)

2026-08-30

Activity Score Changed

Activity score up 17pts (35 → 52)

2026-08-29

Rank Moved

Rank dropped 52 spots (#674 → #726)

2026-08-28

Rank Moved

Rank dropped 21 spots (#653 → #674)

2026-08-27

Rank Moved

Rank dropped 20 spots (#633 → #653)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.6/10

2026-08-26

Rank Moved

Rank rose 484 spots (#1117 → #633)

2026-08-26

HVTrust Changed

HVTrust up 25.5pts (19.3 → 44.8)

2026-08-26

Activity Score Changed

Activity score down 9pts (44 → 35)

2026-08-23

Rank Moved

Rank dropped 24 spots (#1084 → #1108)

2026-08-22

Rank Moved

Rank dropped 46 spots (#1038 → #1084)

2026-08-22

Activity Score Changed

Activity score down 6pts (53 → 47)

2026-08-17

Rank Moved

Rank rose 13 spots (#1044 → #1031)

2026-08-16

Rank Moved

Rank dropped 35 spots (#1009 → #1044)

2026-08-13

Rank Moved

Rank dropped 12 spots (#1001 → #1013)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Withings Health Data

How Withings Health Data could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Withings Health Data compares in MCP Servers

Where the 42.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Withings Health Data

AI agent surface

Maintain Withings Health Data?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers