io.github.cphoskins/cronometer
PYPI · CRONOMETER-MCP
MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods
Available components
Last scanned (12 hours ago)
Scores higher than 94% of PyPI servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to cphoskins/cronometer-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2856 tokens (~105/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_food_entry" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 +27
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 1 Nov 26 −26
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 2.4.1 → 2.4.2 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +1
- Package version: 2.4.0 → 2.4.1 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/cronometer-mcp@2.4.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | cphoskins/cronometer-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/cphoskins/cronometer-mcp/.github/workflows/publish.yml@refs/tags/v2.4.2 |
| Rekor log index | 3632879855 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:894b0315eda7c140c1c45749e9315e3b3a8d24587eef7c02b1dc60798863216e |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_biometric ~122
Add a biometric entry to Cronometer. Supported metric types: weight (lbs), blood_glucose (mg/dL), heart_rate (bpm), body_fat (%). Args: metric_type: One of 'weight', 'blood_glucose', 'heart_rate', 'body_fat'. value: The value in display units (lbs, mg/dL, bpm, %). entry_date: Date as YYYY-MM-DD.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_date | string | yes | – |
| metric_type | string | yes | – |
| value | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
add_food_entry ~329
Add a food entry to the Cronometer diary. Use search_foods to find food_id and food_source_id, then get_food_details for measure_id and weight_grams. For CRDB/custom foods, you can omit measure_id (defaults to a universal NCCDB measure that works for all food sources). When measure_id is omitted, quantity is set to weight_grams. Args: food_id: Numeric food ID from search_foods results. food_source_id: Food source ID from search_foods results. weight_grams: Weight of the serving in grams. date: Date to log the entry as YYYY-MM-DD (e.g. "2026-03-04"). measure_id: Measure/unit ID. Pass 0 (default) to use the universal measure that works for all food sources. quantity: Number of servings. Defaults to weight_grams when measure_id is 0 (universal gram-based measure). diary_group: Diary group name (case-insensitive) or 0-based index. Names are user-configured and are not always Breakfast/Lunch/Dinner/Snacks — call list_diary_groups to see this account's groups. Defaults to a time-of-day choice among enabled groups if omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| diary_group | – | – | – |
| food_id | integer | yes | – |
| food_source_id | integer | yes | – |
| measure_id | integer | – | – |
| quantity | number | – | – |
| weight_grams | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
add_repeat_item ~262
Add a recurring food entry that auto-logs on selected days. Quantity is in default servings for the food (e.g., for coffee where the default serving is 1 cup, quantity=12 means 12 cups). Use search_foods to find food_id and food_source_id. Args: food_id: Numeric food ID from search_foods results. food_source_id: Food source ID from search_foods results. quantity: Number of default servings. food_name: Display name for the food. diary_group: Diary group name (case-insensitive) or 0-based index. Names are user-configured — call list_diary_groups to see this account's groups. Defaults to a time-of-day choice among enabled groups if omitted. days_of_week: Comma-separated day numbers (0=Sun, 1=Mon, ..., 6=Sat), or "all" for every day (default), or "weekdays", or "weekends".
| Name | Type | Req | Description |
|---|---|---|---|
| days_of_week | string | – | – |
| diary_group | – | – | – |
| food_id | integer | yes | – |
| food_name | string | yes | – |
| food_source_id | integer | yes | – |
| quantity | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cancel_active_fast ~62
Cancel an active (in-progress) fast while preserving the recurring schedule. Use get_fasting_history to find active fasts (is_active=true). Args: fast_id: The fast ID of the active fast to cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| fast_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
copy_day ~98
Copy all diary entries from one date to another. Server-side operation that copies ALL entries (food, exercise, notes, biometrics) from source to destination. Additive — does not remove existing entries on the destination date. Args: source_date: Date to copy FROM as YYYY-MM-DD. destination_date: Date to copy TO as YYYY-MM-DD.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_date | string | yes | – |
| source_date | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_macro_template ~180
Create a new saved macro target template in Cronometer. Optionally assigns it to all days of the week as the recurring default. Args: template_name: Name for the new template (e.g. "Retatrutide GI-Optimized"). protein_grams: Protein target in grams. fat_grams: Fat target in grams. carbs_grams: Net carbs target in grams. calories: Calorie target in kcal. assign_to_all_days: If True, also set this as the recurring weekly schedule for all 7 days (default False).
| Name | Type | Req | Description |
|---|---|---|---|
| assign_to_all_days | boolean | – | – |
| calories | number | yes | – |
| carbs_grams | number | yes | – |
| fat_grams | number | yes | – |
| protein_grams | number | yes | – |
| template_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_fast ~48
Delete a fast entry from Cronometer. Use get_fasting_history first to find the fast_id. Args: fast_id: The fast ID to delete.
| Name | Type | Req | Description |
|---|---|---|---|
| fast_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_repeat_item ~52
Delete a recurring food entry. Use get_repeated_items to find the repeat_item_id. Args: repeat_item_id: The ID of the repeat item to delete.
| Name | Type | Req | Description |
|---|---|---|---|
| repeat_item_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_raw_csv ~110
Export raw CSV data from Cronometer for any data type. Useful when you need the full unprocessed export. Args: export_type: One of 'servings', 'daily_summary', 'exercises', 'biometrics', 'notes'. start_date: Start date as YYYY-MM-DD (defaults to today). end_date: End date as YYYY-MM-DD (defaults to today).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | – | – | – |
| export_type | string | yes | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_daily_nutrition ~95
Get daily nutrition summary with macro totals per day. Returns calorie, protein, carb, fat, and fiber totals for each day. Use this for quick daily overviews and trend analysis. Args: start_date: Start date as YYYY-MM-DD (defaults to 7 days ago). end_date: End date as YYYY-MM-DD (defaults to today).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_fasting_history ~88
Get fasting history from Cronometer. Returns all fasts (or fasts within a date range) with their status, names, recurrence rules, and timestamps. Args: start_date: Start date as YYYY-MM-DD (omit for all history). end_date: End date as YYYY-MM-DD (omit for all history).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_fasting_stats ~36
Get aggregate fasting statistics from Cronometer. Returns total fasting hours, longest fast, 7-fast average, and completed fast count.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_food_details ~73
Get detailed food information including available serving measures. Use this after search_foods to get the measure_id needed for add_food_entry. Returns all available serving sizes with their numeric IDs and gram weights. Args: food_source_id: Food source ID from search_foods results.
| Name | Type | Req | Description |
|---|---|---|---|
| food_source_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_food_log ~86
Get detailed food log with individual food entries and full nutrition. Returns every food entry with macros and micronutrients. Great for analyzing what was eaten and spotting nutrient gaps. Args: start_date: Start date as YYYY-MM-DD (defaults to today). end_date: End date as YYYY-MM-DD (defaults to today).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_macro_targets ~97
Get current daily macro targets from Cronometer. Returns the effective macro targets (protein, fat, carbs, calories) and the template name for a specific date or all days of the week. A macro with no target set in Cronometer is null. Args: target_date: Date as YYYY-MM-DD to get targets for (defaults to today). Pass "all" to get the full weekly schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| target_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_micronutrients ~93
Get detailed micronutrient breakdown for meal planning. Shows vitamins, minerals, and other micronutrients per day with period averages. Use this to identify nutrient gaps and plan meals. Args: start_date: Start date as YYYY-MM-DD (defaults to 7 days ago). end_date: End date as YYYY-MM-DD (defaults to today).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_recent_biometrics ~46
Get the most recently logged biometric entries from Cronometer. Returns recent values for weight, blood glucose, blood pressure, heart rate, body fat, and other tracked biometrics.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_repeated_items ~49
List all recurring food entries. Returns all repeat items configured in Cronometer, including their food name, quantity, measure, diary group, and which days of the week they repeat on.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_diary_groups ~104
List this account's diary groups, with the values add_food_entry accepts. Diary group names are user-configured in Cronometer, so they are NOT always Breakfast/Lunch/Dinner/Snacks. Call this before assuming a name exists — an account may rename any slot or enable extra ones. Returns each group's wire_index (the 0-based value add_food_entry takes), its name, and whether it is enabled. Only enabled groups can be written to.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_macro_templates ~44
List all saved macro target templates in Cronometer. Returns template names, IDs, and their macro values. Use this to find the template_name for set_weekly_macro_schedule.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_biometric ~58
Remove a biometric entry from Cronometer. Use get_recent_biometrics to find biometric_id values. Args: biometric_id: The biometric entry ID (e.g. "BXW0DA").
| Name | Type | Req | Description |
|---|---|---|---|
| biometric_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_food_entry ~51
Remove a food entry from the Cronometer diary. Args: serving_id: The serving ID returned by add_food_entry (e.g. "D80lp$").
| Name | Type | Req | Description |
|---|---|---|---|
| serving_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_foods ~76
Search Cronometer's food database by name. Returns matching foods with their IDs and source information needed to add a serving (food_id, food_source_id, measure_id). Args: query: Food name or keyword to search for (e.g. "eggs", "chicken breast").
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_day_complete ~58
Mark a diary day as complete or incomplete. Args: date: Date to mark as YYYY-MM-DD. complete: True to mark complete, False to mark incomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | – | – |
| date | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_macro_targets ~142
Update daily macro targets in Cronometer. Reads current targets first, then updates only the provided values. Omitted values remain unchanged. Args: protein_grams: Protein target in grams. fat_grams: Fat target in grams. carbs_grams: Net carbs target in grams. calories: Calorie target in kcal. target_date: Date as YYYY-MM-DD (defaults to today). template_name: Template name (defaults to "Custom Targets").
| Name | Type | Req | Description |
|---|---|---|---|
| calories | – | – | – |
| carbs_grams | – | – | – |
| fat_grams | – | – | – |
| protein_grams | – | – | – |
| target_date | – | – | – |
| template_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_weekly_macro_schedule ~156
Set the recurring weekly macro schedule by assigning a template to days. This updates the DEFAULT schedule that applies to all future dates, not just a specific date override. First finds the template by name (from existing saved templates or from a recently created per-date template), then assigns it to the specified days of the week. Args: template_name: Name of a saved macro target template (e.g. "Retatrutide GI-Optimized", "Keto Rigorous"). days: Comma-separated day names or "all" (default). E.g. "Monday,Wednesday,Friday" or "all".
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | – |
| template_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sync_cronometer ~171
Download Cronometer data and save locally as JSON + food-log.md. Downloads servings and daily summary data, saves JSON exports, and regenerates food-log.md. Output directory defaults to ~/.local/share/cronometer-mcp/ but can be overridden with the CRONOMETER_DATA_DIR environment variable. Args: start_date: Start date as YYYY-MM-DD (defaults to `days` ago). end_date: End date as YYYY-MM-DD (defaults to today). days: Number of days to look back if start_date not specified (default 14). diet_label: Optional diet label for the markdown header (e.g., "Keto Rigorous").
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| diet_label | – | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.cphoskins/cronometer MCP server?
io.github.cphoskins/cronometer runs locally as a PyPI package, launched with uvx cronometer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cronometer-mcp
claude mcp add cphoskins-cronometer -- uvx cronometer-mcp
What is the io.github.cphoskins/cronometer MCP server?
io.github.cphoskins/cronometer is an MCP server listed in the public MCP registry as io.github.cphoskins/cronometer. MCP server for Cronometer, food logs, macros, fasting, biometrics, and recurring foods. This page covers its PyPI package (cronometer-mcp).
Is the io.github.cphoskins/cronometer MCP server safe to use?
io.github.cphoskins/cronometer scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cphoskins/cronometer MCP server expose?
io.github.cphoskins/cronometer exposes 27 tools: get_food_log, get_daily_nutrition, get_micronutrients, export_raw_csv, list_diary_groups, and 22 more. Their descriptions and schemas cost roughly 2,786 tokens of context every time the server is loaded.
Is the io.github.cphoskins/cronometer MCP server still maintained?
io.github.cphoskins/cronometer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cphoskins/cronometer MCP server under?
io.github.cphoskins/cronometer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.cphoskins/cronometer MCP server?
VerifyMCP ran 16 checks on io.github.cphoskins/cronometer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.