Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
whatevr is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Log meals and read calories and macros from any AI assistant. Pairs with the whatevr iPhone app.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http whatevr-mcp https://api.trywhatevr.app/mcp
# 2 — ask your agent for something these tools do
# log_anything, log_exercise, log_weight and 9 more
whatevr costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TRAll 1 server
trywhatevr1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http whatevr-mcp https://api.trywhatevr.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 exa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | What to log, in plain words. |
| logged_at | string | no | Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'. |
| tz_offset_min | number | no | 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 structured exercise with a known calorie burn. For an ESTIMATED burn from plain text, use log_anything ('30 minute run').
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity | string | yes | e.g. 'running' |
| duration_minutes | number | yes | — |
| calories_burned | number | yes | — |
| logged_at | string | no | Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'. |
| tz_offset_min | number | no | 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 a weigh-in in pounds. The newest reading also becomes the user's current weight (drives their calorie targets).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weight_lb | number | yes | — |
| note | string | no | — |
| logged_at | string | no | Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'. |
| tz_offset_min | number | no | 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 water — glasses (8 fl oz each) or an exact amount_fl_oz. Defaults to 1 glass.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| glasses | number | no | 8 fl oz each; used when amount_fl_oz is absent |
| amount_fl_oz | number | no | — |
| logged_at | string | no | Bare-local timestamp YYYY-MM-DDThh:mm:ss (no zone). Omit to use the user's 'now'. |
| tz_offset_min | number | no | 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). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tz_offset_min | number | no | 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). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD |
Daily calorie/macro/exercise TOTALS over time + the weight trend (no food item names — use get_day for what was actually eaten).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | number | no | 1–730, or 0 for all-time (default 30) |
| anchor | string | no | Window end date (default: the user's today) |
| tz_offset_min | number | no | 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). |
Who the user is: name/handle/email, health profile, calorie/macro targets, and derived metrics.
No parameter schema on file.
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 o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | no | — |
| goal_weight_lb | number | no | — |
| rate_lb_per_week | number | no | Pace for lose/gain (ignored for maintain). |
| activity_level | string | no | — |
| calorie_target | no | 1000–5000, or "auto". | |
| protein_target_g | no | 20–400, or "auto". | |
| carbs_target_g | no | 20–600, or "auto". | |
| fat_target_g | no | 10–250, or "auto". | |
| water_goal_glasses | number | no | — |
| fiber_minimum_g | number | no | — |
| sugar_maximum_g | number | no | — |
| sodium_maximum_mg | number | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| log_reminder | boolean | no | — |
| streak_reminder | boolean | no | — |
| tz_offset_min | number | no | The user's JS getTimezoneOffset(). Only used if the app has never reported their timezone; then it's required. |
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 → Connect
| Parameter | Type | Required | Notes |
|---|---|---|---|
| log_id | string | yes | The item's id from get_today/get_day recent. |
| type | string | yes | The item's type from recent. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| log_id | string | yes | The item's id from get_today/get_day recent (type "food" only). |
| title | string | no | — |
| calories | number | no | — |
| protein_g | number | no | — |
| carbs_g | number | no | — |
| fat_g | number | no | — |
| fiber_g | number | no | — |
| sugar_g | number | no | — |
| sodium_mg | number | no | — |
| meal | string | no | — |
| logged_time | string | no | HH:MM 24h — time-of-day only; the log's DATE never changes. |
| ingredients | array | no | REPLACES the full ingredient list; totals recompute from it. Cannot be combined with top-level numeric fields. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install whatevr or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.2 · scanned 27 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestc9fca45d7d90f17649211fd05c6ed4de71483afc08f3824e9eed4ccb6ecb2d79
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| log_anything | state-write | state-write: declares readOnlyHint: false |
| log_exercise | state-write | state-write: declares readOnlyHint: false |
| log_weight | state-write | state-write: declares readOnlyHint: false |
| log_water | state-write | state-write: declares readOnlyHint: false |
| get_today | no tags | |
| get_day | no tags | |
| get_progress | no tags | |
| get_me | no tags | |
| update_goals | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| update_reminders | state-write | state-write: declares readOnlyHint: false |
| delete_log | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| update_log | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc9fca45d7d90f176
Scanned2026-10-27
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
1.0.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish whatevr can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.