io.github.ekelly95/cronometer-mcp
Cronometer
Is the Cronometer MCP server down? No. It is up and needs env, probed 2026-11-01.
Your Cronometer diary, nutrition with honest coverage (missing is never zero), and safe writes.
needs env probed 2026-11-14 · unchanged since 2026-11-01
MCP error -32603: Internal server error [cronometer-mcp] Credentials are set in the environment but live access is not enabled. Set CRONOMETER_LIVE_ENABLED=1 to
- Run it
- npx -y @ekelly95/cronometer-mcp@1.0.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/ekelly95/cronometer-mcp
- Registry
- active, updated 2026-10-18 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- SlideCraft io.github.eiler2005/slidecraft · alive
- JProfiler io.github.ej-technologies/jprofiler-mcp · alive
- io.github.ejfkdev/zread-mcp · alive
- BrandKit MCP io.github.ejwhite7/brandkit-mcp · alive
- io.github.elagerway/magpipe · needs env
- Umbra io.github.elberacasa/umbra · alive
- io.github.elchin92/avito-mcp · needs env
- io.github.electron-stagewright/core · alive
Servers that mention cronometer.
- io.github.rwestergren/cronometer-api-mcp · install failed
- io.github.cphoskins/cronometer · alive
- Cronometer MCP io.github.atticoos/cronometer-mcp · needs auth
- Cronometer MCP Server and API by Cotlet dev.cotlet/cronometer · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.