MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

wellness-nourish

Earlier Revision Publisher unverified Confidence: Good (0.85)

wellness-nourish is an MCP server published by davidmosiah, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does wellness-nourish support the current MCP specification (2026-07-28)?

Not yet confirmed. wellness-nourish is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is wellness-nourish a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for wellness-nourish (as of 2026-08-20).

How do I connect to wellness-nourish?

wellness-nourish is available via the package npm:wellness-nourish, the official MCP Registry under io.github.davidmosiah/wellness-nourish, the source repository at https://github.com/davidmosiah/wellness-nourish. Authentication: unknown. Transports: stdio.

Does wellness-nourish support MCP revision 2025-11-25?

Yes. wellness-nourish supports MCP revision 2025-11-25 (checked 2026-08-20).

Does wellness-nourish support MCP revision 2026-07-28?

No. wellness-nourish was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were wellness-nourish's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

Local-first nutrition MCP for AI agents: food, barcode, photo, intake, hydration, goals.

Which MCP spec revisions does wellness-nourish support?

wellness-nourish has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is wellness-nourish?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for wellness-nourish

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Stars
8
Forks
2
Last pushed
(48 days ago)
Created
Open issues
0
Primary language
TypeScript
License (repository)
MIT
Continuous integration
Present
Tests
None detected
Security policy
Present

Declared topics: ai-agent-tools, ai-agents, anthropic, barcode, calorie-tracker, claude, claude-desktop, cursor, food-data, health-data, local-first, mcp, mcp-server, model-context-protocol, nutrition, open-food-facts, quantified-self, typescript, usda, wellness — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
0.8.2
Last published
First published
Releases
37
License (package)
MIT
Maintainers
1
Direct dependencies
7
Unpacked size
1.1 MB
Registry signature
Signed
Build provenance
No attestation

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.davidmosiah/wellness-nourish at version 0.7.0 - lists package npm:wellness-nourish and repository https://github.com/davidmosiah/wellness-nourish - accessed
  2. npm registry metadata for wellness-nourish at published version 0.8.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed