Google Health Mcp Unofficial MCP Server
google-health-mcp-unofficial
npm
v0.7.8
Published by davidmosiah — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Unofficial local-first Google Health API v4 MCP server for AI health, sleep and activity agents.
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 − 7 = 93. 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 |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 1
high Shell/command execution in server code (dist/cli/auth.js)MTC-SRC-002
In the server's implementation (`dist/cli/auth.js:18`): 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 { createInterface } from "node:readline"; import { getConfig } from "../s
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/cli/auth.js
Tools 26
Each tool and what it can reach — statically extracted from the published source.
google_health_agent_manifestno sensitive capabilitygoogle_health_cache_statusno sensitive capabilitygoogle_health_capabilitiesno sensitive capabilitygoogle_health_connection_statusno sensitive capabilitygoogle_health_daily_rollupno sensitive capabilitygoogle_health_daily_summaryno sensitive capabilitygoogle_health_data_inventoryno sensitive capabilitygoogle_health_data_type_coverageno sensitive capabilitygoogle_health_demono sensitive capabilitygoogle_health_exchange_codeno sensitive capability
Show 16 more tools ↓
google_health_get_auth_urlno sensitive capabilitygoogle_health_get_identityno sensitive capabilitygoogle_health_get_profileno sensitive capabilitygoogle_health_get_settingsno sensitive capabilitygoogle_health_list_data_pointsno sensitive capabilitygoogle_health_list_data_typesno sensitive capabilitygoogle_health_onboardingno sensitive capabilitygoogle_health_privacy_auditno sensitive capabilitygoogle_health_profile_getno sensitive capabilitygoogle_health_profile_updateno sensitive capabilitygoogle_health_quickstartno sensitive capabilitygoogle_health_reconcile_data_pointsno sensitive capabilitygoogle_health_revoke_accessno sensitive capabilitygoogle_health_rollupno sensitive capabilitygoogle_health_weekly_summaryno sensitive capabilitygoogle_health_wellness_contextno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (26 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 8
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.7.8 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
v0.7.7 |
A 93/100 | 1 | 1.13.0 | 2026-08-29 |
v0.7.6 |
A 93/100 | 1 | 1.13.0 | 2026-08-25 |
v0.7.5 |
A 93/100 | 1 | 1.12.1 | 2026-08-14 |
v0.7.3 |
A 93/100 | 1 | 1.12.1 | 2026-08-10 |
Show 3 more versions ↓
v0.7.1 |
A 93/100 | 1 | 1.12.1 | 2026-08-03 |
v0.5.7 |
A 93/100 | 1 | 1.12.1 | 2026-08-01 |
v0.5.3 |
A 93/100 | 1 | 1.12.1 | 2026-07-29 |
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-unofficial --onlineMore in Data Science & ML
MCP server for 2s.io — 575+ pay-per-call tools for AI agents — ground-truth data, AI gateway, and agent infra (storage, locks, queues, watchers). x402 USDC on Base/Solana, no API keys, upto usage billing, free trials.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Add MCP servers to your favorite coding agents with a single command.
Help agents automatically write and test stories for your UI components
Model Context Protocol server for AI-Archive platform - enables AI agents to discover, submit, and review research papers
MCP server for Semantic Scholar research workflows with stdio and Streamable HTTP transports.