Health and biology · MCP server
Wellness nourish: MCP server, setup and security
Wellness nourish is an open-source MCP server that lets an AI agent track meals and hydration and generate daily summaries of intake. Its repository has 11 stars and its last commit is from October 17, 2026 and it is licensed under MIT.
| Adoption (stars) | 10/40 | |
|---|---|---|
| Maintenance | 30/30 | |
| Framework (licence, registry, official) | 20/30 |
What Wellness nourish does
According to its repository: “Nutrition and hydration tracking: food search, barcode lookup, meal estimation, intake logs and daily summaries.”
An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Wellness nourish is listed under Health and biology, a category of 37 servers in the directory, where it ranks #26 by stars.
Topics declared by the repository: ai-agents, claude, food-data, health-data, local-first, nutrition.
Installing and connecting Wellness nourish
Distribution modes declared in the official MCP registry:
- npm package (Node.js, usually started with
npx)
Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript. Listed systems: macOS, Windows, Linux.
Security: what to check
An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.
None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Wellness nourish. That does not replace reading the code.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on May 5, 2026, the davidmosiah/wellness-nourish repository has 11 stars and 2 forks, with 1 open issues. It has more stars than 28% of the servers in the directory. It received changes this month. Version published in the registry: 0.7.0 (July 13, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Wellness nourish is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Listed in the official MCP registry
- Permissive licence (MIT)
Limitations
- Few visible users
Alternatives
- Medplum2.8K ★
- Pyscn1.1K ★
- Biomcp662 ★
- FHIR MCP Server (wso2)136 ★
- HealthChain229 ★
- Google health MCP72 ★
Learn more
Frequently asked questions
How do I install Wellness nourish?
Wellness nourish is distributed as npm package (Node.js, usually started with npx). Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of davidmosiah/wellness-nourish.
Is Wellness nourish free?
The code is published under the MIT licence and can be used free of charge.
Is Wellness nourish safe?
No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.
Is it an official server?
Nothing says so: it is a project published by davidmosiah on GitHub. Check who maintains it before giving it access.
What are the alternatives to Wellness nourish?
In the same category: Medplum, Pyscn, Biomcp, and FHIR MCP Server (wso2). Medplum and Pyscn score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score