whatevr

Working · 2.6 s

app.trywhatevr/whatevrv1.0.2 Domain verified

Log meals and read calories and macros from any AI assistant. Pairs with the whatevr iPhone app.

Health & Science

Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://api.trywhatevr.app/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

get_day Read-only

Everything 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.

datestring, required

YYYY-MM-DD

Tools (9)

get_day

read-only

Argument	Type	Description
date*	string	YYYY-MM-DD

Input schema (JSON)

{
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "YYYY-MM-DD"
    }
  }
}

get_me

Who the user is: name/handle/email, health profile, calorie/macro targets, and derived metrics.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {}
}

get_progress

Daily calorie/macro/exercise TOTALS over time + the weight trend (no food item names — use get_day for what was actually eaten).

read-only

Argument	Type	Description
days	number	1–730, or 0 for all-time (default 30)
anchor	string	Window end date (default: the user's today)
tz_offset_min	number	The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one).

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "days": {
      "type": "number",
      "description": "1–730, or 0 for all-time (default 30)"
    },
    "anchor": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Window end date (default: the user's today)"
    },
    "tz_offset_min": {
      "type": "number",
      "description": "The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one)."
    }
  }
}

get_today

Today'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 correct mistakes.

read-only

Argument	Type	Description
tz_offset_min	number	The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one).

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "tz_offset_min": {
      "type": "number",
      "description": "The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one)."
    }
  }
}

log_anything

Log 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 dates like 'yesterday I had pizza' work. Describe the FOOD, not just numbers: stating explicit nutrition in the text ('burrito, 800 calories') pins those totals exactly but logs ONE pre-computed item with no ingredient breakdown — if you do that, follow up with update_log's `ingredients` array so the log keeps its per-item detail.

Argument	Type	Description
text*	string	What to log, in plain words.
logged_at	string	Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'.
tz_offset_min	number	The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one).

Input schema (JSON)

{
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "maxLength": 2000,
      "description": "What to log, in plain words."
    },
    "logged_at": {
      "type": "string",
      "description": "Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'."
    },
    "tz_offset_min": {
      "type": "number",
      "description": "The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one)."
    }
  }
}

log_exercise

Log structured exercise with a known calorie burn. For an ESTIMATED burn from plain text, use log_anything ('30 minute run').

Argument	Type	Description
activity*	string	e.g. 'running'
logged_at	string	Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'.
tz_offset_min	number	The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one).
calories_burned*	number
duration_minutes*	number

Input schema (JSON)

{
  "type": "object",
  "required": [
    "activity",
    "duration_minutes",
    "calories_burned"
  ],
  "properties": {
    "activity": {
      "type": "string",
      "description": "e.g. 'running'"
    },
    "logged_at": {
      "type": "string",
      "description": "Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'."
    },
    "tz_offset_min": {
      "type": "number",
      "description": "The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one)."
    },
    "calories_burned": {
      "type": "number",
      "maximum": 20000,
      "minimum": 0
    },
    "duration_minutes": {
      "type": "number",
      "maximum": 1440,
      "minimum": 1
    }
  }
}

log_water

Log water — glasses (8 fl oz each) or an exact amount_fl_oz. Defaults to 1 glass.

Argument	Type	Description
glasses	number	8 fl oz each; used when amount_fl_oz is absent
logged_at	string	Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'.
amount_fl_oz	number
tz_offset_min	number	The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one).

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "glasses": {
      "type": "number",
      "maximum": 32,
      "minimum": 1,
      "description": "8 fl oz each; used when amount_fl_oz is absent"
    },
    "logged_at": {
      "type": "string",
      "description": "Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'."
    },
    "amount_fl_oz": {
      "type": "number",
      "maximum": 256,
      "minimum": 1
    },
    "tz_offset_min": {
      "type": "number",
      "description": "The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one)."
    }
  }
}

log_weight

Log a weigh-in in pounds. The newest reading also becomes the user's current weight (drives their calorie targets).

Argument	Type	Description
note	string
logged_at	string	Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'.
weight_lb*	number
tz_offset_min	number	The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one).

Input schema (JSON)

{
  "type": "object",
  "required": [
    "weight_lb"
  ],
  "properties": {
    "note": {
      "type": "string"
    },
    "logged_at": {
      "type": "string",
      "description": "Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'."
    },
    "weight_lb": {
      "type": "number",
      "maximum": 1500,
      "minimum": 20
    },
    "tz_offset_min": {
      "type": "number",
      "description": "The user's JS getTimezoneOffset() — minutes BEHIND UTC (e.g. 240 for EDT). Optional: when omitted, the user's app-reported timezone is used (UTC only if the account has never reported one)."
    }
  }
}

update_log

Correct 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 are absolute for the item as logged. Two modes, never mixed: send `ingredients` to REPLACE the whole list (include every ingredient you want kept — the log's totals recompute from it, so don't also send calories/macros), OR send top-level numbers to set totals directly — the existing ingredient breakdown then RESCALES proportionally so the parts always sum to the new totals (ingredient names/amounts don't change, so when the COMPOSITION changed — something added or removed — send `ingredients` instead). Note: ANY edit that changes a routine-created log's title or its calories — including an ingredients replacement, since totals recompute — also updates that saved routine. When logged_time changes, the log's meal may re-infer from the new hour unless you set meal explicitly. Requires a full-access token; edit one log at a time.

destructive

Argument	Type	Description
meal	string
fat_g	number
title	string
log_id*	string	The item's `id` from get_today/get_day `recent` (type "food" only).
carbs_g	number
fiber_g	number

{ "type": "object", "required": [ "log_id" ], "properties": { "meal": { "enum": [ "breakfast", "lunch", "dinner", "snack" ], "type": "string" }, "fat_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "title": { "type": "string", "maxLength": 200 }, "log_id": { "type": "string", "description": "The item's `id` from get_today/get_day `recent` (type \"food\" only)." }, "carbs_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "fiber_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "sugar_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "calories": { "type": "number", "maximum": 20000, "minimum": 0 }, "protein_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "sodium_mg": { "type": "number", "maximum": 100000, "minimum": 0 }, "ingredients": { "type": "array", "items": { "type": "object", "required": [ "name", "calories" ], "properties": { "name": { "type": "string", "maxLength": 120 }, "fat_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "amount": { "type": "string", "maxLength": 60 }, "carbs_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "fiber_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "sugar_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "calories": { "type": "number", "maximum": 20000, "minimum": 0 }, "protein_g": { "type": "number", "maximum": 2000, "minimum": 0 }, "sodium_mg": { "type": "number", "maximum": 100000, "minimum": 0 } } }, "maxItems": 50, "description": "REPLACES the full ingredient list; totals recompute from it. Cannot be combined with top-level numeric fields." }, "logged_time": { "type": "string", "pattern": "^\\d{2}:\\d{2}$", "description": "HH:MM 24h — time-of-day only; the log's DATE never changes." } } }