updated 2026-10-11 08:08 UTC

Nutrition MCP

Repository Website by akutishevsky

A remote MCP server for personal nutrition tracking — log meals, track macros, and review nutrition history through conversation.

MCP Servers TypeScript Listed MIT

Is Nutrition MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 28%
Last push yesterday
Compare Nutrition MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Nutrition MCP scores 55.0/100 (Grade C), ranked #813 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 28% of recent commits are signed; last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Nutrition MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Nutrition MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/akutishevsky/nutrition-mcp, MIT, last pushed 2026-10-10. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Sep 25, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages None

    No registry package. Nutrition MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 4.2/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Nutrition MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Nutrition MCP compares in MCP Servers

  1. #441 Licinexus MCP 55.1 +0.1
  2. #442 Bimwright 55.1 +0.1
  3. #443 Nutrition MCP 55.0 this agent
  4. #444 Paper Distill MCP 54.9 −0.1
  5. #445 SunoMCP 54.9 −0.1

Bars show each HVTrust score; the tick marks Nutrition MCP’s 55.0.

Where the 55.0 comes from

HVTrust dimensions vs the MCP Servers average

55.0 / 100 · 100.0% confidence

Nutrition MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.7 / 25
3.7 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
4.5 / 20
2.9 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-03
Rank Moved
Rank dropped 27 spots (#777 → #804)
2026-09-28
Rank Moved
Rank rose 23 spots (#807 → #784)
2026-09-27
Rank Moved
Rank rose 52 spots (#859 → #807)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Nutrition MCP View MCP Servers Report missing data
68.2
Activity sub-score · out of 100
#443
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 08:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
75
Forks
29
Last Push
2026-10-10
yesterday
Commits (4 wk)
286
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
13
Rank Change
▲8
was #821

Analysis

Activity Inputs

68.2 / 100
StarsRepository reach
11.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.9 / 20

Common questions about Nutrition MCP

Nutrition MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Nutrition MCP publish package provenance?
No published build provenance is currently detected for Nutrition MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Nutrition MCP have an OpenSSF Scorecard?
Nutrition MCP has an OpenSSF Scorecard score of 4.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Nutrition MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Nutrition MCP use?
Nutrition MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Nutrition MCP's commits signed?
28% of the last 100 commits to Nutrition MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Nutrition MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Nutrition MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Supabase
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Nutrition MCP?

For maintainers

HVTrust scores Nutrition MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 26Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-03
Rank Moved
Rank dropped 27 spots (#777 → #804)
2026-09-28
Rank Moved
Rank rose 23 spots (#807 → #784)
2026-09-27
Rank Moved
Rank rose 52 spots (#859 → #807)
2026-09-26
Rank Moved
Rank rose 16 spots (#875 → #859)
2026-09-25
Rank Moved
Rank dropped 18 spots (#857 → #875)
2026-09-24
Rank Moved
Rank dropped 24 spots (#833 → #857)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Supabase
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 364 spots (#469 → #833)
2026-09-23
HVTrust Changed
HVTrust up 10.2pts (43.3 → 53.5)
2026-09-22
Newly Listed
First tracked at rank #469
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 16 spots (#816 → #800)
2026-09-11
Rank Moved
Rank dropped 10 spots (#787 → #797)
2026-09-09
Rank Moved
Rank dropped 12 spots (#782 → #794)
2026-09-07
Rank Moved
Rank dropped 33 spots (#740 → #773)
2026-09-06
Rank Moved
Rank dropped 10 spots (#730 → #740)
2026-09-05
Rank Moved
Rank dropped 72 spots (#658 → #730)
2026-09-04
Rank Moved
Rank dropped 24 spots (#634 → #658)
2026-09-03
Rank Moved
Rank dropped 30 spots (#604 → #634)
2026-09-02
Rank Moved
Rank dropped 31 spots (#573 → #604)
2026-09-01
Rank Moved
Rank dropped 17 spots (#556 → #573)
2026-08-31
Rank Moved
Rank dropped 25 spots (#531 → #556)
2026-08-29
Rank Moved
Rank dropped 26 spots (#507 → #533)
2026-08-27
Rank Moved
Rank dropped 11 spots (#492 → #503)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.2/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 430 spots (#922 → #492)
2026-08-26
HVTrust Changed
HVTrust up 30.9pts (23.1 → 54.0)
2026-08-23
Rank Moved
Rank dropped 13 spots (#904 → #917)
2026-08-22
Rank Moved
Rank rose 18 spots (#922 → #904)
2026-08-19
Rank Moved
Rank dropped 12 spots (#913 → #925)
2026-08-16
Rank Moved
Rank dropped 21 spots (#908 → #929)
2026-08-10
Rank Moved
Rank dropped 52 spots (#853 → #905)
2026-08-08
Newly Listed
First tracked at rank #841
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 55.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/nutrition-mcp.svg)](https://hvtracker.net/agents/nutrition-mcp)
HTML:
<a href="https://hvtracker.net/agents/nutrition-mcp"><img src="https://hvtracker.net/badge/nutrition-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON