PeptideLab Calculator vs io.github.cphoskins/cronometer
PeptideLab Calculator is an MCP server published by rigorpeptides.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-28. 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
| Marketplace |  io.github.cphoskins/cronometer | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 No figure published Not marked · First seen |
Listed Version: 2.4.0 Downloads/month (PyPI): 3 239 Downloads/week (PyPI): 388 Forks (GitHub): 15 Stars (GitHub): 27 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): 27 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
| Fact | PeptideLab Calculator | io.github.cphoskins/cronometer |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 27 |
| Forks (GitHub) (differs) | No figure on GitHub | 15 |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | Remote server (rigorpeptides.com/mcp) | On your machine (cronometer-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/cphoskins/cronometer-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (4 h ago) | no remote endpoint we check |
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
PeptideLab Calculator
Research-use peptide reconstitution & dosing calculators for 15 compounds. Not medical advice.
io.github.cphoskins/cronometer
MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods
How to run each
PeptideLab Calculator As a remote MCP server
claude mcp add --transport http peptidelab https://rigorpeptides.com/mcpio.github.cphoskins/cronometer As a local MCP server: PyPI package
claude mcp add --env "CRONOMETER_PASSWORD=<YOUR_CRONOMETER_PASSWORD>" --env "CRONOMETER_USERNAME=<YOUR_CRONOMETER_USERNAME>" --transport stdio cronometer -- uvx cronometer-mcpRequires: CRONOMETER_PASSWORD (secret), CRONOMETER_USERNAME
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only PeptideLab Calculator 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 PeptideLab Calculator publish no settings it asks for, so we do not compare settings.
What it can do: PeptideLab Calculator · What it can do: io.github.cphoskins/cronometer · 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.