updated 2026-08-12 05:02 UTC

Withings Health Data

akutishevsky/withings-mcp

MCP server for Withings health data integration

MCP Servers TypeScript Grade D Listed MIT
20.5/100
Rank #1042 of 1283
Compare Withings Health Data

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-27 · 16d ago
Recent change
Rank +1

Is Withings Health Data safe? Withings Health Data scores 20.5/100 (Grade D), ranked #1042 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 31% of recent commits are signed; last pushed 2026-07-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#562 spreadsheet-kit MCP — 20.6 (D) → #563 App Publish MCP — 20.6 (D) → #565 Kibana — 20.5 (D) → #566 Nslookup MCP — 20.5 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 59 spots (#984 → #1043)
2026-08-08
Newly Listed
First tracked at rank #942
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 Withings Health Data View MCP Servers Report missing data
53.9
Activity sub-score · out of 100
#564
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 16 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
33
Forks
8
Last Push
2026-07-27
16 days ago
Commits (4 wk)
24
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▲3
was #1045

Analysis

HVTrust Dimensions vs MCP Servers

20.5 / 100 · 50.0% confidence

Withings Health Data MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.6 / 25
3.4 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
16.5 / 20
4.1 above avg 12.4
AdoptionLog-scaled stars · package downloads
3.7 / 20
2.1 below avg 5.8

Activity Inputs

53.9 / 100
StarsRepository reach
9.2 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
17.4 / 25
CommunityFork signal
4.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
31%
of last 100 commits verified

Is Withings Health Data safe?

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?
No OpenSSF Scorecard data is currently published for Withings Health Data. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Withings Health Data actively maintained?
Maintained. Last push was 16 days ago.
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?
31% 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
high confidence
Declared
Declared plugin/integration surface detected.
  • database
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

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
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 59 spots (#984 → #1043)
2026-08-08
Newly Listed
First tracked at rank #942
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 20.5 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON