Is Nutrition MCP safe to use?

Nutrition MCP has an HVTrust score of 52.2/100 (Grade C), ranked #872 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Nutrition MCP?

Nutrition MCP scores 52.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 63 GitHub stars and is categorized under MCP Servers.

Nutrition MCP

akutishevsky/nutrition-mcp

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? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10

Provenance None

Signed commits 18%

Last push 2d ago

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 52.2/100 (Grade C), ranked #872 of 1325 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; 18% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Nutrition MCP compares in MCP Servers

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

Where the 52.2 comes from

HVTrust dimensions vs the MCP Servers average

52.2 / 100 · 100.0% confidence

Nutrition MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

6.2 / 25

4.1 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.1 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.8 / 20

5.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

4.3 / 20

2.9 below avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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

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

60.7

Activity sub-score · out of 100

#494

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-24

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #875

Analysis

Activity Inputs

60.7 / 100

StarsRepository reach

10.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

18.4 / 25

CommunityFork signal

6.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

18%

of last 100 commits verified

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

Common questions about Nutrition MCP

Public trust evidence for Nutrition MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

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 2 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?

18% 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.

Supabase

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

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 →

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON