healthstylz-mcp
Related Servers
Alternatives to healthstylz-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to query authoritative medical sources such as FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, medical literature, health statistics, clinical guidelines, and pediatric resources through local MCP tools.97 npmISC

citedhealth-mcpofficial
AlicenseNot gradedqualityDmaintenanceMCP server for CITED Health that allows AI assistants to query evidence-based supplement data, including ingredient evidence grades, health conditions, PubMed papers, glossary terms, and educational guides.MIT- AlicenseNot gradedqualityAmaintenanceEnables users to query WHOOP recovery, sleep, HRV, strain, workouts, and personal health analytics in natural language through MCP clients such as Claude, Codex, and GitHub Copilot. It also provides read-only tools, resources, prompts, and local performance dashboards for reviewing trends and readiness evidence.17 npmMIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides authoritative medical data from FDA, WHO, PubMed, RxNorm, and Google Scholar, enabling drug information lookup, health statistics retrieval, medical literature searching, and clinical guidelines access directly in AI workflows.97 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query health metrics such as activity, blood pressure, glucose, heart rate, sleep, and SpO2 from a PostgreSQL-backed wellness database, returning structured data and summaries through MCP tools.-
- AlicenseAqualityCmaintenanceEvidence-based supplement recommendation MCP server covering 17 supplements and 40+ conditions with medication interaction checking and form quality classification.560 npmMIT
TDQS
Scored across 7 tools
Most tools target distinct topics, but the curtain pair is genuinely confusable: get_curtain_guides and get_curtain_window_wellness_specs both cover fabric GSM and sizing, forcing an agent to guess which to call for a spec question. get_daily_wellness_brief and search_healthstylz_articles also overlap on content discovery, and herbs vs. supplements could blur for queries like elderberry.
Every tool follows a predictable snake_case verb_noun pattern (get_*, search_*, lookup_*, calculate_*), with the domain subject clearly encoded in the name. The verbs differ but consistently reflect the action type rather than violating convention.
Seven tools is well within the appropriate range and each maps to a distinct content area (curtains, herbs, news, articles, supplements, cost calculator). The surface reads as a curated grab-bag of niches rather than an over- or under-built set.
Coverage is uneven across the sub-domains: curtains get both guides and specs, and supplements get both evidence lookup and a cost calculator, but articles support only search with no get_article/full-text retrieval, and herbs have no evidence or sourcing counterpart to the guide reader. These are notable gaps for a content site, though agents can partially work around them.