← MetricBridge

Security

Last reviewed 29 October 2026. For security reviewers, integrators and anyone who wants to check rather than trust.

MetricBridge is local-first and read-only: there is no account and no developer server in the health-data path, so the developer is never in a position to leak it. This page lists what is hardened, how to verify each claim yourself, and how to report a problem. The plain-language version, one row per data flow, is the privacy receipt.

In one screen

Inside the app

Supply-chain integrity

npm. health-export-mcp 1.8.0 was published by the repository's GitHub Actions release workflow with npm publish --provenance. The registry holds a Sigstore-signed SLSA provenance attestation (predicate https://slsa.dev/provenance/v1) that links the tarball to the exact commit and workflow run that built it, and the npm package page shows the provenance badge. Versions 1.6.0 and earlier were published by hand and have registry signatures but no provenance.

GitHub releases. Each release carries the tarball, the .mcpb bundle, a CycloneDX SBOM (health-export-mcp-1.8.0.cdx.json), a SHA256SUMS file and SHA256SUMS.minisig, a minisign signature made offline with key 951BA54856154FBA. Signed checksums start with v1.6.0.

This site's mirror (/mcp/*.mjs, used by the agent setup skill) is covered by the same key: SHA256SUMS lists every file and SHA256SUMS.minisig signs the list (trusted comment: "healthexport.dev/mcp artifacts, health-export-mcp 1.8.0"). The public key is published from a second, independent source (the GitHub repository and SKILL.md), so a compromise of this origin alone cannot swap both an artifact and its key. Pin it from there, not from here. CI re-verifies the signature on every change (scripts/verify-minisig.mjs), so a rebuilt checksum file that could not be re-signed cannot be published.

The MCP server itself is about 4,000 lines of plain ES modules with zero runtime dependencies and no build step: what is on npm is what is in the repository, which you can read in one sitting. It makes no outbound network calls; a grep for fetch(, http. and net. in server.mjs and healthstore.mjs comes back empty.

Checks you can run

Every claim above and below has a command. Fail closed on any mismatch.

# 1. Verify the site mirror's signature and checksums (needs minisign: brew install minisign)
PUBKEY='RWS6TxVWSKUblYkx7Db6ZpmvHALwHpznZpjaED/FlZj+PpxSlel0MxHZ'   # pin from the GitHub repo
curl -fsSLO https://www.healthexport.dev/mcp/SHA256SUMS
curl -fsSLO https://www.healthexport.dev/mcp/SHA256SUMS.minisig
minisign -Vm SHA256SUMS -P "$PUBKEY" || { echo "signature INVALID: do not run"; exit 1; }
curl -fsSLO https://www.healthexport.dev/mcp/server.mjs
shasum -a 256 --ignore-missing -c SHA256SUMS || { echo "checksum mismatch: do not run"; exit 1; }

# 2. Verify the npm package's registry signature and provenance attestation
mkdir verify-hx && cd verify-hx && npm init -y >/dev/null
npm install health-export-mcp@1.8.0 && npm audit signatures

# 3. Confirm the server makes no outbound network calls
grep -nE 'fetch\(|https?\.|net\.|dns\.' node_modules/health-export-mcp/server.mjs node_modules/health-export-mcp/healthstore.mjs

# 4. Site headers, DNS and TLS
curl -sI https://www.healthexport.dev/ | grep -iE 'content-security-policy|strict-transport|x-frame|cross-origin|permissions-policy'
dig +short healthexport.dev CAA
dig +short _dmarc.healthexport.dev TXT
dig @1.1.1.1 +dnssec healthexport.dev A | grep -E 'flags:.* ad|RRSIG'
openssl s_client -connect www.healthexport.dev:443 -tls1_1 </dev/null 2>&1 | grep -i 'no protocols'
curl -s https://hstspreload.org/api/v2/status?domain=healthexport.dev

What runs on this site

Styles, fonts and images are served from this origin. Two things measure traffic, and we would rather name them than let you find them in the network tab.

Neither runs anywhere near your health data. The MCP server carries no telemetry at all. The iOS app carries no health telemetry; it does carry Meta's SDK for advert attribution, as set out above and in full on the privacy page.

Transport and domain hardening

Configured in site/_headers and at the DNS; each line is checkable with the commands above.

Report a vulnerability

Please do not open a public issue for a security problem. Either route reaches the developer directly:

Include the version (npx -y health-export-mcp --doctor prints the server's; the app's is under Settings), what you observed and how to reproduce it. Use synthetic data (--demo serves a synthetic dataset): never send real health data, pairing codes or export passphrases. Fixes ship as a new version on top of the latest release; older versions are not patched. Machine-readable contact details, with an expiry date so you can tell the file is maintained, are at /.well-known/security.txt (RFC 9116). The full policy for the server is SECURITY.md.

What this page does not claim

MetricBridge · Wellness information, not medical advice. · Home · What you get · On-device AI · Readiness · Methods · MCP server · GitHub · Changelog · Privacy · Security · Support · Press · Terms · Accessibility · Get the app