io.github.davidmosiah/samsung-health-mcp
NPM · SAMSUNG-HEALTH-MCP-UNOFFICIAL
Unofficial local-first MCP server for Samsung Health personal-data CSV/ZIP exports.
Available components
Last scanned (10 hours ago)
Scores higher than 87% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1836 tokens (~79/item across 23 items; 18 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +2
- Source repository: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 12 Oct 26 −4
- Provenance: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/samsung-health-mcp-unofficial@0.5.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
samsung_health_agent_manifest Samsung Health Agent Manifest ~42
Machine-readable install, runtime and privacy guidance for AI agents operating Samsung Health export data.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_capabilities Samsung Health MCP Capabilities ~38
Explain supported Samsung Health export data, unavailable live Samsung Health access, privacy modes and recommended agent workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_clear_incremental_cache Clear Samsung Health Incremental Import Cache ~109
Manually clear the incremental import cache at ~/.samsung-health-mcp/incremental-cache.json. The cache tracks the latest parsed timestamp per Samsung Health record category so subsequent `samsung_health_list_records` calls (with `incremental_cache: true`) skip already-seen records. Use this when you want to force a full re-parse without changing the export file. The cache also auto-invalidates when the export file mtime changes.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_connection_status Samsung Health Connection Status ~47
Check local Samsung Health export path, Node version, privacy mode and Hermes client posture without reading full export data.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_daily_summary Samsung Health Daily Summary ~91
Build a daily wellness summary from local Samsung Health export data. It is not live Samsung Health and not medical advice.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD local date. Defaults to today in the configured timezone. |
| response_format | string | – | – |
| timezone | string | – | IANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC. |
No output schema declared.
No examples provided.
samsung_health_data_inventory Samsung Health Data Inventory ~106
Scan the local Samsung Health export once and report available record types, workouts, date coverage, freshness and safe next calls.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Optional ISO date/time upper bound. |
| privacy_mode | string | – | – |
| response_format | string | – | – |
| start | string | – | Optional ISO date/time lower bound. |
| timezone | string | – | IANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC. |
No output schema declared.
No examples provided.
samsung_health_demo Samsung Health Demo ~59
Returns realistic example payloads of samsung_health_daily_summary, samsung_health_weekly_summary, and samsung_health_wellness_context with Galaxy-Watch-style values, so agents see the contract before parsing a real export.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_export_freshness Samsung Health Export Freshness ~113
Check how recently the local Samsung Health export directory/CSVs were written. Returns mtime, days_since_export, an is_stale flag, and a recommendation. Considered stale if the export is older than 30 days, or older than 7 days with no recent records (the inventory's latest-record date is also older than 7 days). Use before relying on samsung_health_daily_summary or samsung_health_wellness_context to confirm the export is fresh.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_list_records List Samsung Health Records ~153
List bounded records from local Samsung Health CSV/ZIP export data. Use type/start/end filters to keep output small.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Optional ISO date/time upper bound. |
| incremental_cache | boolean | – | When true and `type` is set, skip records already seen in a previous call (per-category cache at ~/.samsung-health-mcp/incremental-cache.json). Cache auto-invalidates when the export file mtime chang… |
| limit | integer | – | – |
| privacy_mode | string | – | – |
| response_format | string | – | – |
| start | string | – | Optional ISO date/time lower bound. |
| type | string | – | Samsung Health record type, e.g. samsung_health_steps. |
No output schema declared.
No examples provided.
samsung_health_list_workouts List Samsung Health Workouts ~74
List bounded workout records from local Samsung Health CSV/ZIP export data.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Optional ISO date/time upper bound. |
| limit | integer | – | – |
| privacy_mode | string | – | – |
| response_format | string | – | – |
| start | string | – | Optional ISO date/time lower bound. |
No output schema declared.
No examples provided.
samsung_health_onboarding Delx Wellness Onboarding Flow ~123
Return the 11-question onboarding flow plus the current profile state and missing fields. Read-only — does NOT persist anything. Pair with samsung_health_profile_update once the user answers. Cross-connector: the same profile is shared by every Delx Wellness MCP (whoop, garmin, oura, fitbit, strava, polar, withings, apple-health, samsung-health, google-health, nourish, cycle-coach, cgm, air).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Onboarding locale. Defaults to en. |
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_privacy_audit Samsung Health Privacy Audit ~33
Return the local privacy and export-file posture without revealing health data.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_profile_get Get Delx Wellness Profile ~92
Read the shared Delx Wellness profile from ~/.delx-wellness/profile.json. Returns preferred name, goals, devices, training/nutrition/exercise/agent preferences and safety flags. NEVER contains OAuth tokens or API secrets — this connector is local-export and has no cloud auth, but the profile contract is the same across every Delx Wellness MCP. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_profile_update Update Delx Wellness Profile ~153
Persist a partial patch to ~/.delx-wellness/profile.json. Requires explicit_user_intent=true (otherwise returns USER_ACTION_REQUIRED). Rejects secret-like fields (oauth, token, secret, password, cookie, refresh, api_key, session) at write time. Use to record preferred name, goals, devices, training context, nutrition context, exercise preferences, agent preferences, and safety flags.
| Name | Type | Req | Description |
|---|---|---|---|
| explicit_user_intent | boolean | – | Must be true to persist. Prevents accidental writes from agent inference. |
| patch | object | yes | Partial WellnessProfileDocument patch. Top-level keys: profile, goals, devices, training, nutrition, preferences, safety, notes. |
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_quickstart Samsung Health Quickstart ~93
Personalized 3-step setup walkthrough for the human user. Adapts to current state (is SAMSUNG_HEALTH_EXPORT_PATH set? does the export folder/CSV/zip exist and parse?). Call this first when the user asks 'how do I connect Samsung Health?'. This connector is local-first and never touches Samsung, Health Connect, or any cloud API.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_reimport Reimport Samsung Health Export from Watch Folder ~187
Re-scan the configured watch folder (SAMSUNG_HEALTH_WATCH_PATH or `setup --watch-path <dir>`) for a newer Samsung Health export. If a newer SamsungHealth folder / *.csv / *samsung*health*.zip is found, it is promoted to the active export, the in-memory snapshot cache and incremental cache are cleared, and subsequent summaries reflect the new data. With check_only=true, only report what would happen without promoting. This is the cross-platform recurring-refresh path — the native Android Health Connect bridge needs an Android device and is separate.
| Name | Type | Req | Description |
|---|---|---|---|
| check_only | boolean | – | When true, report the watch-folder status without promoting a new export. |
| force | boolean | – | When true, re-promote the newest export in the folder even if it already matches the active export (forces a cache refresh). |
| response_format | string | – | – |
No output schema declared.
No examples provided.
samsung_health_weekly_summary Samsung Health Weekly Summary ~109
Build a weekly wellness summary from local Samsung Health export data. It is not live Samsung Health and not medical advice.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| end_date | string | – | YYYY-MM-DD local end date. Defaults to today in the configured timezone. |
| privacy_mode | string | – | – |
| response_format | string | – | – |
| timezone | string | – | IANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC. |
No output schema declared.
No examples provided.
samsung_health_wellness_context Samsung Health Wellness Context ~113
Normalize local Samsung Health export sleep, workout and activity data into the shared wellness_context shape for recommendation engines.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD local date. Defaults to today in the configured timezone. |
| injury_flags | array | – | – |
| notes | string | – | – |
| response_format | string | – | – |
| soreness | array | – | – |
| timezone | string | – | IANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC. |
No output schema declared.
No examples provided.
How do I install the io.github.davidmosiah/samsung-health-mcp server?
io.github.davidmosiah/samsung-health-mcp runs locally as an npm package, launched with npx -y samsung-health-mcp-unofficial. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · samsung-health-mcp-unofficial
claude mcp add davidmosiah-samsung-health-mcp -- npx -y samsung-health-mcp-unofficial
What is the io.github.davidmosiah/samsung-health-mcp server?
io.github.davidmosiah/samsung-health-mcp is listed in the public MCP registry as io.github.davidmosiah/samsung-health-mcp. Unofficial local-first MCP server for Samsung Health personal-data CSV/ZIP exports. This page covers its npm package (samsung-health-mcp-unofficial).
Is the io.github.davidmosiah/samsung-health-mcp server safe to use?
io.github.davidmosiah/samsung-health-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.davidmosiah/samsung-health-mcp server expose?
io.github.davidmosiah/samsung-health-mcp exposes 18 tools: samsung_health_agent_manifest, samsung_health_capabilities, samsung_health_connection_status, samsung_health_quickstart, samsung_health_demo, and 13 more. Their descriptions and schemas cost roughly 1,735 tokens of context every time the server is loaded.
Is the io.github.davidmosiah/samsung-health-mcp server still maintained?
io.github.davidmosiah/samsung-health-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.davidmosiah/samsung-health-mcp server under?
io.github.davidmosiah/samsung-health-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.davidmosiah/samsung-health-mcp server?
VerifyMCP ran 16 checks on io.github.davidmosiah/samsung-health-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.