io.github.atticoos/cronometer-mcp

Cronometer MCP

Is the Cronometer MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Review nutrition, log meals, and manage foods and recipes in your Cronometer account.

needs auth probed 2026-11-14 · HTTP 401 · Bearer

1tools, from the package cronometer-mcp

85tokens in Claude Opus 5.5

<0.1 %of Claude's 200k window

The server needs auth, so these tool definitions were read from the publisher's open-source package npm:cronometer-mcp, started in a container with placeholder values and the network off, on 2026-11-14. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.

Streamable HTTP error: Error POSTing to endpoint:

Endpoint: https://mcp.cronometer-mcp.dev/mcp (streamable-http)
Host: mcp.cronometer-mcp.dev
Of a 1M window: <0.1 % of a 1M context window
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.cronometer-mcp.dev/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcp.cronometer-mcp.dev, PKCE S256, grants authorization_code, refresh_token.
Scopes cronometer:read.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/atticoos/cronometer-mcp
Website: https://cronometer-mcp.dev
Registry: active, updated 2026-11-07 · registry entry

Compare this server with others.

More servers

Servers that mention cronometer.

io.github.rwestergren/cronometer-api-mcp · install failed
io.github.cphoskins/cronometer · alive
Cronometer io.github.ekelly95/cronometer-mcp · needs env
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.

Atom feed

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 answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.