updated 2026-11-10 04:07 UTC

Cronometer Api MCP

Repository

MCP server for Cronometer nutrition tracking via the mobile REST API

MCP Servers Python Listed MIT

Is Cronometer Api MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.9 / 10
Provenance Attested
Signed commits 92%
Last push 2d ago
Advisories None known
Compare Cronometer Api MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Cronometer Api MCP scores 75.4/100 (Grade B), ranked #263 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.9/10; 92% of recent commits are signed; no published advisory affects its latest release (cronometer-api-mcp); last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cronometer Api 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 Cronometer Api MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/rwestergren/cronometer-api-mcp, MIT, last pushed 2026-11-08. 92% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.9/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

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

  3. Published packages Partly attested

  4. What you install today No known advisories

    Latest release checked: cronometer-api-mcp 0.2.6. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-31 OSSF Scorecard: 4.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Cronometer Api 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 Cronometer Api MCP compares in MCP Servers

  1. #151 Oxylabs MCP 75.5 +0.1
  2. #152 Sec Edgar MCP 75.4 ±0
  3. #153 Cronometer Api MCP 75.4 this agent
  4. #154 ITASCA MCP Server 75.3 −0.1
  5. #155 Satelliteoflove Godot MCP 75.1 −0.3

Bars show each HVTrust score; the tick marks Cronometer Api MCP’s 75.4.

Where the 75.4 comes from

HVTrust dimensions vs the MCP Servers average

75.4 / 100 · 100.0% confidence

Cronometer Api MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.2 / 25
7.4 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
16.8 / 20
4.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.7 / 20
in line with avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-11-08
Rank Moved
Rank rose 58 spots (#319 → #261)
2026-11-07
Rank Moved
Rank rose 10 spots (#329 → #319)
2026-11-05
Rank Moved
Rank dropped 50 spots (#280 → #330)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent
View MCP Servers Report missing data
58.8
Activity sub-score · out of 100
#153
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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
71
Forks
40
Last Push
2026-11-08
2 days ago
Commits (4 wk)
16
Downloads (7d)
277
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▼2
was #261

Analysis

Activity Inputs

58.8 / 100
StarsRepository reach
11.1 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
15.3 / 25
CommunityFork signal
7.5 / 20

Common questions about Cronometer Api MCP

Public supply-chain signals for Cronometer Api MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Cronometer Api MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Cronometer Api MCP publish package provenance?
Yes. Cronometer Api MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Cronometer Api MCP have an OpenSSF Scorecard?
Cronometer Api MCP has an OpenSSF Scorecard score of 4.9/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 Cronometer Api MCP actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Cronometer Api MCP use?
Cronometer Api MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cronometer Api MCP's commits signed?
92% of the last 100 commits to Cronometer Api 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
medium confidence
Implemented
Cronometer Api MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Cronometer Api 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
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Cronometer Api MCP?

For maintainers

HVTrust scores Cronometer Api 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 24HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-08
Rank Moved
Rank rose 58 spots (#319 → #261)
2026-11-07
Rank Moved
Rank rose 10 spots (#329 → #319)
2026-11-05
Rank Moved
Rank dropped 50 spots (#280 → #330)
2026-11-03
Rank Moved
Rank rose 38 spots (#314 → #276)
2026-11-02
Rank Moved
Rank rose 20 spots (#334 → #314)
2026-11-01
Rank Moved
Rank dropped 12 spots (#322 → #334)
2026-10-29
Rank Moved
Rank dropped 56 spots (#270 → #326)
2026-10-26
Rank Moved
Rank rose 61 spots (#323 → #262)
2026-10-25
Rank Moved
Rank dropped 57 spots (#266 → #323)
2026-10-05
Rank Moved
Rank rose 10 spots (#262 → #252)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 624 spots (#871 → #247)
2026-09-23
HVTrust Changed
HVTrust up 46.3pts (27.4 → 73.7)
2026-09-22
Newly Listed
First tracked at rank #871
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank dropped 10 spots (#222 → #232)
2026-09-05
Rank Moved
Rank dropped 53 spots (#168 → #221)
2026-09-03
Rank Moved
Rank dropped 11 spots (#158 → #169)
2026-08-31
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-31
Grade Changed
Trust grade C → B
2026-08-31
Rank Moved
Rank rose 143 spots (#288 → #145)
2026-08-31
HVTrust Changed
HVTrust up 9.9pts (64.2 → 74.1)
2026-08-30
Rank Moved
Rank rose 18 spots (#306 → #288)
2026-08-29
Rank Moved
Rank dropped 15 spots (#291 → #306)
2026-08-28
Rank Moved
Rank dropped 11 spots (#280 → #291)
2026-08-26
Rank Moved
Rank dropped 22 spots (#249 → #271)
2026-08-24
Rank Moved
Rank dropped 10 spots (#230 → #240)
2026-08-22
Rank Moved
Rank rose 26 spots (#257 → #231)
2026-08-19
Rank Moved
Rank dropped 15 spots (#243 → #258)
2026-08-17
Rank Moved
Rank rose 13 spots (#258 → #245)
2026-08-13
Rank Moved
Rank dropped 18 spots (#240 → #258)
GitHub → PyPI: cronometer-api-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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