open-health-sync

MCP server · GitHub · ★ 54 · graded 2026-10-19Source linked

Open source health data aggregator and self-hosted Terra alternative. One API for wearable data from Apple Health, Health Connect, Oura, WHOOP, Withings, Fitbit, Dexcom and more: REST, FHIR R4, Open mHealth, webhooks, CSV/Parquet and a read-only MCP server. One Go binary plus Postgres. AGPL-3.0.

No outside reports on file

open-health-sync connects to external service APIs; restrict its folder reach, network access, and credentials before installing.

Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for Open Health Sync helpful?

What it can access

Local filesNo local folder access notedLOW
Command executionNo shell command runner notedLOW
Network reachConnects to outside service APINOTED
CredentialsNo API token requiredLOW
Package sourceGitHub (soma-intelligence/open-health-sync)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

No npm or PyPI package is listed. Install from source: github.com/soma-intelligence/open-health-sync ↗

All setup options ↓

Check this skill Watch it in my stack Compare README badge View project

Everything known

We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.

0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30

Popularity grade: D (from public signals such as stars and downloads, not a code review). Graded 2026-10-19.

Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.

Check a specific version →

About Open Health Sync

Open Health Sync is an MCP server focused on Data & databases and Web & browsing: Open source health data aggregator and self-hosted Terra alternative. One API for wearable data from Apple Health, Health Connect, Oura, WHOOP, Withings, Fitbit, Dexcom and more: REST, FHIR R4, Open mHealth, webhooks, CSV/Parquet and a read-only MCP server. One Go binary plus Postgres. AGPL-3.0.

It is hosted on GitHub at soma-intelligence/open-health-sync (54 GitHub stars). Based on its public metadata, its operational scope includes: connects to outside service api.

Setup

These use the package this listing points to. Check the project’s own instructions before running anything.

No npm or PyPI package is listed for this MCP server. Source code and setup steps: github.com/soma-intelligence/open-health-sync.

Why this grade

DD — High risk signals

Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.

Popularity and upkeep

24/100

GitHub stars: 54
Listing last refreshed: 2026-10-29

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Risks to watch for

External API & account scope: Connects to third-party service APIs. Use a dedicated, least-privilege token scoped only to the workspaces or repositories this tool needs.
Dependency & version pinning: Distributed via GitHub (soma-intelligence/open-health-sync). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

Check its activity history or logs weekly at first, and look at what it changed or sent.
Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

It asks for more access than its job requires, or prompts you to paste passwords.
It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install Open Health Sync?

Open Health Sync does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/soma-intelligence/open-health-sync.

Are there security reports about Open Health Sync?

No reports found for this package in our research (last checked 2026-10-30). Open Health Sync currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.

Is Open Health Sync actively maintained?

Open Health Sync has 54 GitHub stars. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/soma-intelligence/open-health-sync before pinning it in production.

What are alternatives to Open Health Sync?

You can compare Open Health Sync side by side with other Postgres MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.

Maintain or use Open Health Sync? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade D for Open Health Sync

GitHub README Markdown:

markdown

[![AgentArmorHQ Risk Grade for Open Health Sync](https://agentarmorhq.com/api/badge/soma-intelligence-open-health-sync)](https://agentarmorhq.com/skills/soma-intelligence-open-health-sync)

HTML embed:

html

<a href="https://agentarmorhq.com/skills/soma-intelligence-open-health-sync"><img src="https://agentarmorhq.com/api/badge/soma-intelligence-open-health-sync" alt="AgentArmorHQ Risk Grade for Open Health Sync" height="20" /></a>

Terminal check:

terminal

curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "soma-intelligence-open-health-sync"

Share with your security lead

Need sign-off to use open-health-sync? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: open-health-sync
- **Listing URL:** https://agentarmorhq.com/skills/soma-intelligence-open-health-sync
- **Type:** App connector
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0
- **Public Adoption:** 54 GitHub stars

#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Connects to outside service API
- **Credentials:** No API token required
- **Package source:** GitHub (soma-intelligence/open-health-sync)

#### Recommended Hardened Setup
- **Source Repo:** https://github.com/soma-intelligence/open-health-sync
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type: App connector
Publisher: soma-intelligence
Source code: github.com/soma-intelligence/open-health-sync
Est. context load: ~600 tokens / turn (~3 tool schemas, 0.3% of 200k context)
Popularity: 54 GitHub stars
Last updated: 2026-10-29
Last graded: 2026-10-19

Community

Discussions for Open Health Sync

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for Open Health Sync helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude