Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.davidmosiah/samsung-health-mcp

NPM · SAMSUNG-HEALTH-MCP-UNOFFICIAL · SCANNED AUG 3

Unofficial local-first MCP server for Samsung Health personal-data CSV/ZIP exports.

+19 this week 69 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (96 of 97), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (96 of 97), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · samsung-health-mcp-unofficial

# add to Claude Code
claude mcp add davidmosiah-samsung-health-mcp -- npx -y samsung-health-mcp-unofficial
# add to Codex CLI
codex mcp add davidmosiah-samsung-health-mcp -- npx -y samsung-health-mcp-unofficial
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "davidmosiah-samsung-health-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "samsung-health-mcp-unofficial"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add davidmosiah-samsung-health-mcp --command npx --arg -y --arg samsung-health-mcp-unofficial
# ~/.hermes/config.yaml
mcp_servers:
  davidmosiah-samsung-health-mcp:
    command: "npx"
    args: ["-y", "samsung-health-mcp-unofficial"]
// mcp.json
{
  "mcpServers": {
    "davidmosiah-samsung-health-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "samsung-health-mcp-unofficial"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +48
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Stability: unverified → 0.23 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • Schema quality: unverified → 100 functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 1 Aug 26 +7
    • Malware scan: unverified → pass security
    • Tool coverage: 100 → unverified functional
  • 31 Jul 26 −37
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 50

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 96 deprecated · 30 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 18 exposed · ~1,735 tokens

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.

Tool Tokens
samsung_health_agent_manifest ~42

Machine-readable install, runtime and privacy guidance for AI agents operating Samsung Health export data.

NameTypeReqDescription
clientstring
response_formatstring

No output schema declared.

No examples provided.

samsung_health_capabilities ~38

Explain supported Samsung Health export data, unavailable live Samsung Health access, privacy modes and recommended agent workflow.

NameTypeReqDescription
response_formatstring

No output schema declared.

No examples provided.

samsung_health_clear_incremental_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.

NameTypeReqDescription
response_formatstring

No output schema declared.

No examples provided.

samsung_health_connection_status ~47

Check local Samsung Health export path, Node version, privacy mode and Hermes client posture without reading full export data.

NameTypeReqDescription
clientstring
response_formatstring

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
datestringYYYY-MM-DD local date. Defaults to today in the configured timezone.
response_formatstring
timezonestringIANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC.

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
endstringOptional ISO date/time upper bound.
privacy_modestring
response_formatstring
startstringOptional ISO date/time lower bound.
timezonestringIANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC.

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
response_formatstring

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
response_formatstring

No output schema declared.

No examples provided.

samsung_health_list_records ~153

List bounded records from local Samsung Health CSV/ZIP export data. Use type/start/end filters to keep output small.

NameTypeReqDescription
endstringOptional ISO date/time upper bound.
incremental_cachebooleanWhen 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…
limitinteger
privacy_modestring
response_formatstring
startstringOptional ISO date/time lower bound.
typestringSamsung Health record type, e.g. samsung_health_steps.

No output schema declared.

No examples provided.

samsung_health_list_workouts ~74

List bounded workout records from local Samsung Health CSV/ZIP export data.

NameTypeReqDescription
endstringOptional ISO date/time upper bound.
limitinteger
privacy_modestring
response_formatstring
startstringOptional ISO date/time lower bound.

No output schema declared.

No examples provided.

samsung_health_onboarding ~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).

NameTypeReqDescription
localestringOnboarding locale. Defaults to en.
response_formatstring

No output schema declared.

No examples provided.

samsung_health_privacy_audit ~33

Return the local privacy and export-file posture without revealing health data.

NameTypeReqDescription
response_formatstring

No output schema declared.

No examples provided.

samsung_health_profile_get ~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.

NameTypeReqDescription
response_formatstring

No output schema declared.

No examples provided.

samsung_health_profile_update ~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.

NameTypeReqDescription
explicit_user_intentbooleanMust be true to persist. Prevents accidental writes from agent inference.
patchobjectyesPartial WellnessProfileDocument patch. Top-level keys: profile, goals, devices, training, nutrition, preferences, safety, notes.
response_formatstring

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
response_formatstring

No output schema declared.

No examples provided.

samsung_health_reimport ~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.

NameTypeReqDescription
check_onlybooleanWhen true, report the watch-folder status without promoting a new export.
forcebooleanWhen true, re-promote the newest export in the folder even if it already matches the active export (forces a cache refresh).
response_formatstring

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
daysinteger
end_datestringYYYY-MM-DD local end date. Defaults to today in the configured timezone.
privacy_modestring
response_formatstring
timezonestringIANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC.

No output schema declared.

No examples provided.

samsung_health_wellness_context ~113

Normalize local Samsung Health export sleep, workout and activity data into the shared wellness_context shape for recommendation engines.

NameTypeReqDescription
datestringYYYY-MM-DD local date. Defaults to today in the configured timezone.
injury_flagsarray
notesstring
response_formatstring
sorenessarray
timezonestringIANA timezone, e.g. America/Fortaleza. Defaults to SAMSUNG_HEALTH_TIMEZONE or UTC.

No output schema declared.

No examples provided.