Ext Ops Panel
Open dashboard
Comparison

io.github.cphoskins/cronometer vs Nibb — Food log

io.github.cphoskins/cronometer is an MCP server published by cphoskins. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Nibb — Food log is an MCP server published by nibb.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplaceio.github.cphoskins/cronometerNibb — Food log
Official MCP Registry Listed
Version: 2.4.0
Downloads/month (PyPI): 3 239
Downloads/week (PyPI): 388
Forks (GitHub): 15
Stars (GitHub): 27
Not marked · First seen
Listed
Version: 0.2.0
No figure published
Not marked · First seen
PyPI (MCP servers) Listed
Version: 2.4.0
Downloads/month (PyPI): 3 239
Downloads/week (PyPI): 388
Forks (GitHub): 15
Stars (GitHub): 27
Not marked · First seen
Not listed

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

io.github.cphoskins/cronometer vs Nibb — Food log
Factio.github.cphoskins/cronometerNibb — Food log
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)27No figure on GitHub
Forks (GitHub) (differs)15No figure on GitHub
Last release (differs)2026-10-25Not published
Where it runs (differs)On your machine (cronometer-mcp)Remote server (nibb.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/cphoskins/cronometer-mcpNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days ago, requires a key

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

io.github.cphoskins/cronometer

In its own words, on Official MCP Registry:

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

Nibb — Food log

In its own words, on Official MCP Registry:

Log meals, change portions, manage targets, and read trends in your Nibb food journal.

How to run each

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

Nibb — Food log As a remote MCP server

Claude Code
claude mcp add --transport http nibb https://nibb.io/mcp

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

Only Nibb — Food log has a remote endpoint we check. How we check endpoints

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 Nibb — Food log publish no settings it asks for, so we do not compare settings.

What it can do: io.github.cphoskins/cronometer · What it can do: Nibb — Food log · Compare two other plugins

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