Skip to content

whatevr MCP server

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

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

12 tools: 3 can delete or cancel things, 5 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the whatevr MCP server can do

The whatevr MCP server is published by trywhatevr.app, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (3 tools: update_goals, delete_log and update_log) and create or change data (5 tools: log_anything, log_exercise, log_weight, log_water and 1 more). 4 tools only read.

1 tool reads private data (get_me); 1 tool brings in text other people can write (get_me).

The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.2.

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.

12 tools

Deletes or cancels 3Claude Code: deny
  • delete_logDelete ONE entry from the user's log: a food, exercise, weigh-in or water entry.No findings

    Why it is in this group

    • The name "delete_log" says "delete": a word for removing or ending something.
    • The description says "can't be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete 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 remaining one. This can't be undone, so confirm with the user first. Needs the user's "Delete entries" switch for this connection (whatevr app → Settings → Connections). The user is notified.

    Annotations the server declares

    • title: Delete a logged entry
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • update_goalsChange the user's goal and daily targets — the same settings as the app's Goals screen.No findings

    Why it is in this group

    • The name "update_goals" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Change 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 calories and macros consistent (protein×4 + carbs×4 + fat×9 ≈ calories), so the targets it returns can differ slightly from what you sent — report the returned ones. Current weight is not here: log a weigh-in with log_weight. Needs the user's "Change goals & settings" switch for this connection (whatevr app → Settings → Connections); if it's off you'll get a message saying so — relay it. The user is notified of every change.

    Annotations the server declares

    • title: Change goals & targets
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • 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 5Claude 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
  • update_remindersTurn the user's daily reminders on or off: the evening 'nothing logged today' nudge and the streak reminder.No findings

    Why it is in this group

    • The name "update_reminders" says "update": a word for a change.
    Description, as the server wrote it
    Turn 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 notified of the change.

    Annotations the server declares

    • title: Turn reminders on or off
    • 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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:23 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.trywhatevr.app/.well-known/oauth-protected-resource
Authorization servers
https://api.trywhatevr.app
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (3 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.trywhatevr.app/mcp: tools/list returned 12 tools to an anonymous client, including update_goals (destructive), delete_log (destructive), update_log (destructive), log_anything (write), log_exercise (write) and 3 more

    What this check looks for

Posture changes

  1. Nov 3, 2026
    • Tools that change things, listed without credentials: 5 to 8

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.

  1. Tools3 added.+3 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 8.View diff
    • Tools that change things, listed without credentials: 5 to 8

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",
      "mcp__whatevr__update_reminders"
    ],
    "deny": [
      "mcp__whatevr__update_goals",
      "mcp__whatevr__delete_log",
      "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://radar.anlyon.com/api/v1/servers/app.trywhatevr/whatevr/verify?hash=ffadc92560cecd6e9db9209add0ef43d6fd786285ee21a4d07394d3195e44f0b" | jq -e '.changed == false'

Pinned hash ffadc92560ce, from Nov 9, 2026, 06:18 UTC.

Watch

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

https://radar.anlyon.com/servers/app.trywhatevr/whatevr/changes.xml

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

Badge

Anlyon Radar badge for app.trywhatevr/whatevr
[![Anlyon Radar](https://radar.anlyon.com/badge/app.trywhatevr/whatevr.svg)](https://radar.anlyon.com/servers/app.trywhatevr/whatevr)

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

whatevr MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the whatevr MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the whatevr MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: update_goals, delete_log and update_log.

Can the whatevr MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the whatevr MCP server have?

12 tools: 3 destructive, 5 write, 4 read. update_goals, delete_log, update_log, log_anything, log_exercise, log_weight, log_water, update_reminders and 4 more.

Does the whatevr MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the whatevr MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the whatevr MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.