
whatevr — AI calorie tracker MCP server
Which MCP servers are whatevr — AI calorie tracker's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-29
- Registry nameapp.trywhatevr/whatevrverified in the MCP registry
The registry name sits under trywhatevr.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-29
- Tools12
- Server calls itselfwhatevr
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 321 ms.
- Its tools do log a meal by speaking it to the phone; have an AI agent record meals over MCP, but not scan a barcode to log packaged food.
- Checked on 5 of the 7 days it takes to judge reliability.
Once connected
- For "log a meal by speaking it to the phone", the likely first call is log_anything.
- For "have an AI agent record meals over MCP", the likely first call is log_anything.
- update_goals, update_reminders, delete_log, update_log change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 6 of 12 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- What an agent can do with it2 of 3 use cases
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer332 ms
- Space in an agent's context≈ 2,781 tokensthe definitions of all its tools (12), which an agent carries on every turn
- Tool definitionsA · 92 of 100
- Typed results0 of 12 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 6 of 12
What an agent can do with it
- can do · log a meal by speaking it to the phone
- cannot · scan a barcode to log packaged food
- can do · have an AI agent record meals over MCP
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: update_goals, update_reminders, delete_log, update_log
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
log_anythingLog food, drinks, water, exercise, or a weigh-in from one natural-language sentence — the same parser as the app's voice logging. Examples: 'two eggs and toast', '30 minute run', '3 glasses of water', 'weighed 184 this morning'. Spoken…
log_exerciseLog structured exercise with a known calorie burn. For an ESTIMATED burn from plain text, use log_anything ('30 minute run').
log_weightLog a weigh-in in pounds. The newest reading also becomes the user's current weight (drives their calorie targets).
log_waterLog water — glasses (8 fl oz each) or an exact amount_fl_oz. Defaults to 1 glass.
get_todayToday's complete picture: calorie/macro totals vs targets, water, streak, exercises, and the item-by-item food log (`recent`: every logged item's name, calories, macros, ingredients). Each `recent` item's `id` works with update_log to…
get_dayEverything logged on a specific day, INCLUDING each food item's name and nutrition (same shape as get_today). Use this to answer “what did I eat yesterday / on <date>”. Each `recent` item's `id` works with update_log to correct mistakes.
get_progressDaily calorie/macro/exercise TOTALS over time + the weight trend (no food item names — use get_day for what was actually eaten).
get_meWho the user is: name/handle/email, health profile, calorie/macro targets, and derived metrics.
update_goalsChange the user's goal and daily targets — the same settings as the app's Goals screen. Send ONLY the fields to change. Each target takes a number (a custom target) or "auto" (computed from their body, activity and goal). The server keeps…
update_remindersTurn the user's daily reminders on or off: the evening 'nothing logged today' nudge and the streak reminder. Same as the app's Notifications screen. Needs the user's "Change goals & settings" switch for this connection. The user is…
delete_logDelete ONE entry from the user's log: a food, exercise, weigh-in or water entry. Read get_today/get_day first — each item in `recent` carries its `id` and `type`; pass both. Deleting a weigh-in updates their current weight to the newest…
update_logCorrect an existing FOOD log: title, nutrition numbers, the ingredient list, meal, or time-of-day. Read get_today/get_day first — each item in `recent` (type "food") carries the `id` to pass here. Send ONLY the fields to change; values…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"whatevr": {
"type": "http",
"url": "https://api.trywhatevr.app/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http trywhatevr https://api.trywhatevr.app/mcpclaude.ai, ChatGPT and other clients: add https://api.trywhatevr.app/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.