Google Health MCP Server
google-health-mcp
npm
v0.3.0
Source verified
Published by gorban-dev — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for the Google Health API: log meals and water, read sleep, activity and nutrition. Bring-your-own Google Cloud credentials.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
high Shell/command execution in server code (dist/oauth.js)MTC-SRC-002
In the server's implementation (`dist/oauth.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { createHash, randomBytes } from "node:crypto"; import { createServer } f
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/oauth.js
medium Hardcoded egress to an external endpoint (dist/version.js)MTC-SRC-003
In the server's implementation (`dist/version.js:14`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const res = await fetch("https://registry.npmjs.org/google-health-mcp/latest", { signal: AbortSignal.t
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/version.js
Tools 20
Each tool and what it can reach — statically extracted from the published source.
delete_food_logno sensitive capabilityget_activity_rangeno sensitive capabilityget_daily_summaryno sensitive capabilityget_food_logno sensitive capabilityget_health_overviewno sensitive capabilityget_heart_rate_rangeno sensitive capabilityget_hrvno sensitive capabilityget_nutrition_rangeno sensitive capabilityget_profileno sensitive capabilityget_sleepno sensitive capability
Show 10 more tools ↓
get_sleep_rangeno sensitive capabilityget_weight_rangeno sensitive capabilityget_workoutsno sensitive capabilitylog_foodno sensitive capabilitylog_food_from_dbno sensitive capabilitylog_mealno sensitive capabilitylog_waterno sensitive capabilitylog_weightno sensitive capabilitysearch_foodno sensitive capabilityupdate_food_logno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 3
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.3.0 latest |
A 94/100 | 2 | 1.14.0 | 2026-09-25 |
v0.2.0 |
A 94/100 | 2 | 1.12.1 | 2026-07-27 |
v0.1.0 |
A 93/100 | 1 | 1.10.0 | 2026-07-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan google-health-mcp --onlineMore in Lifestyle & Local
7Timer! MCP.
MCP server for Australian address search and validation via Addressr
Admissions data & match scores for law, medical, dental, MBA, pharmacy, vet, optometry schools
Live AI data for agents: model releases, regulations (EU AI Act), GenAI glossary, daily news.
EPA AirNow MCP — official US real-time AQI + forecast (free key)
MCP server for the [Open-Meteo Air Quality API](https://air-quality-api.open-meteo.com) — current air quality conditions and hourly forecasts by location. Free, no auth required.