Ext Ops Panel
Open dashboard
Comparison

fitness-tools vs io.github.cphoskins/cronometer

fitness-tools is a plugin bundle for AI coding tools published by jeffallan. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.cphoskins/cronometer is an MCP server published by cphoskins. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacefitness-toolsio.github.cphoskins/cronometer
Community marketplace jeffallan/fitness-tools Listed
Version: 1.0.1
Forks (GitHub): 5
Stars (GitHub): 18
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.4.0
Downloads/month (PyPI): 3 239
Downloads/week (PyPI): 388
Forks (GitHub): 15
Stars (GitHub): 26
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 2.4.0
Downloads/month (PyPI): 3 239
Downloads/week (PyPI): 388
Forks (GitHub): 15
Stars (GitHub): 26
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

fitness-tools vs io.github.cphoskins/cronometer
Factfitness-toolsio.github.cphoskins/cronometer
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)18 (worse)26 (better)
Forks (GitHub) (differs)5 (worse)15 (better)
Last release (differs)Not published2026-10-25
Where it runs (differs)Installs as a plugin bundleOn your machine (cronometer-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)3Not a bundle
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/jeffallan/fitness-toolsgithub.com/cphoskins/cronometer-mcp
Changes in the last 7 days22
First seen (differs)2026-10-232026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

fitness-tools

In its own words, on Community GitHub marketplaces:

3 specialized fitness skills providing body composition assessment (Durnin-Womersley, Jackson-Pollock 3/4/7-site), one-rep max estimation (validated percentage table), and macronutrient meal planning (ectomorph, mesomorph, endomorph body types). Powered by the fitness-tools Python library.

io.github.cphoskins/cronometer

In its own words, on Official MCP Registry:

MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods

How to run each

fitness-tools As a Claude Code plugin

Claude Code
/plugin marketplace add jeffallan/fitness-tools
/plugin install fitness-tools@fitness-tools

io.github.cphoskins/cronometer As a local MCP server: PyPI package

Claude Code
claude mcp add --env "CRONOMETER_PASSWORD=<YOUR_CRONOMETER_PASSWORD>" --env "CRONOMETER_USERNAME=<YOUR_CRONOMETER_USERNAME>" --transport stdio cronometer -- uvx cronometer-mcp

Requires: CRONOMETER_PASSWORD (secret), CRONOMETER_USERNAME

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of fitness-tools publish no settings it asks for, so we do not compare settings.

What it can do: fitness-tools · What it can do: io.github.cphoskins/cronometer · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built