Skip to content

whatevr

app.trywhatevr/whatevrtrywhatevr.appstreamable-httpv1.0.2Scanned

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

9 tools: 1 can delete or cancel things, 4 change things and 4 only read.

Tools: 1 delete, 0 irreversible, 4 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 4 findings

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • update_logCorrect an existing FOOD log: title, nutrition numbers, the ingredient list, meal, or time-of-day.No findings

    Why it is in this group

    • The name "update_log" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Fix a logged item
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 4Claude Code: ask
  • log_anythingLog food, drinks, water, exercise, or a weigh-in from one natural-language sentence — the same parser as the app's voice logging.1 finding

    Why it is in this group

    • The name "log_anything" says "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "log_anything" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_anything" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Log by describing it
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • log_exerciseLog structured exercise with a known calorie burn.1 finding

    Why it is in this group

    • The name "log_exercise" says "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "log_exercise" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_exercise" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Log structured exercise with a known calorie burn. For an ESTIMATED burn from plain text, use log_anything ('30 minute run').

    Annotations the server declares

    • title: Log exercise
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • log_waterLog water — glasses (8 fl oz each) or an exact amount_fl_oz.1 finding

    Why it is in this group

    • The name "log_water" says "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "log_water" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_water" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Log water — glasses (8 fl oz each) or an exact amount_fl_oz. Defaults to 1 glass.

    Annotations the server declares

    • title: Log water
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • log_weightLog a weigh-in in pounds.1 finding

    Why it is in this group

    • The name "log_weight" says "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "log_weight" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_weight" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Log a weigh-in in pounds. The newest reading also becomes the user's current weight (drives their calorie targets).

    Annotations the server declares

    • title: Log a weigh-in
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • get_dayEverything logged on a specific day, INCLUDING each food item's name and nutrition (same shape as get_today).No findings

    Why it is in this group

    • The name "get_day" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: A specific day's log
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_meWho the user is: name/handle/email, health profile, calorie/macro targets, and derived metrics.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_me" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Who the user is: name/handle/email, health profile, calorie/macro targets, and derived metrics.

    Annotations the server declares

    • title: Profile & targets
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_progressDaily calorie/macro/exercise TOTALS over time + the weight trend (no food item names — use get_day for what was actually eaten).No findings

    Why it is in this group

    • The name "get_progress" says "get": a word for reading.
    Description, as the server wrote it
    Daily calorie/macro/exercise TOTALS over time + the weight trend (no food item names — use get_day for what was actually eaten).

    Annotations the server declares

    • title: Progress & trends
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • 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, ingredient…No findings

    Why it is in this group

    • The name "get_today" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Today's log & totals
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

4 warn
  • The server marks "log_anything" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_anything" says "log": a word for reading.

    What this check looks for
  • The server marks "log_exercise" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_exercise" says "log": a word for reading.

    What this check looks for
  • The server marks "log_weight" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_weight" says "log": a word for reading.

    What this check looks for
  • The server marks "log_water" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "log_water" says "log": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http whatevr https://api.trywhatevr.app/mcp
claude mcp add --transport http whatevr https://api.trywhatevr.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__whatevr__get_today",
      "mcp__whatevr__get_day",
      "mcp__whatevr__get_progress",
      "mcp__whatevr__get_me"
    ],
    "ask": [
      "mcp__whatevr__log_anything",
      "mcp__whatevr__log_exercise",
      "mcp__whatevr__log_weight",
      "mcp__whatevr__log_water"
    ],
    "deny": [
      "mcp__whatevr__update_log"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as whatevr. Review it before you use it.

Capability tags behind 1 rule
  • mcp__whatevr__get_me private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/app.trywhatevr/whatevr/verify?hash=80b7733460e336f0bbad09fe546bf43d93b8b91a62613a16b65845fa99763907" | jq -e '.changed == false'

Pinned hash 80b7733460e3, from Oct 25, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/app.trywhatevr/whatevr/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for app.trywhatevr/whatevr
[![anlyon.dev](https://anlyon.dev/badge/app.trywhatevr/whatevr.svg)](https://anlyon.dev/servers/app.trywhatevr/whatevr)

Source: MCP Registry. Synced Oct 25, 2026, 19:17 UTC.