{"name":"app.trywhatevr/whatevr","title":"whatevr","url":"https://api.trywhatevr.app/mcp","host":"api.trywhatevr.app","read_at":"2026-11-10T15:26:19.326217+00:00","grade":"A","score":100,"capped":null,"graded":true,"pending_second_read":[],"counts":{"error":0,"warning":0,"info":1},"findings":[{"rule":"mcp-version-differs","severity":"info","message":"The version it reports differs from its newest registry entry. It reports 1.0.0; the registry lists 1.0.2.","fix":"","where":[],"count":0}],"handshake":{"answered":true,"mcp":true,"era":"handshake","protocol_version":"2025-06-18","server_info":{"name":"whatevr","version":"1.0.0","title":"whatevr — food & health logging"},"capabilities":["tools"]},"sign_in":null,"tools":[{"name":"log_anything","title":null,"description":"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.","read_only":false,"destructive":false,"inputs":["text","logged_at","tz_offset_min"],"required":["text"],"price_stated_usd":null},{"name":"log_exercise","title":null,"description":"Log structured exercise with a known calorie burn. For an ESTIMATED burn from plain text, use log_anything ('30 minute run').","read_only":false,"destructive":false,"inputs":["activity","duration_minutes","calories_burned","logged_at","tz_offset_min"],"required":["activity","duration_minutes","calories_burned"],"price_stated_usd":null},{"name":"log_weight","title":null,"description":"Log a weigh-in in pounds. The newest reading also becomes the user's current weight (drives their calorie targets).","read_only":false,"destructive":false,"inputs":["weight_lb","note","logged_at","tz_offset_min"],"required":["weight_lb"],"price_stated_usd":null},{"name":"log_water","title":null,"description":"Log water — glasses (8 fl oz each) or an exact amount_fl_oz. Defaults to 1 glass.","read_only":false,"destructive":false,"inputs":["glasses","amount_fl_oz","logged_at","tz_offset_min"],"required":[],"price_stated_usd":null},{"name":"get_today","title":null,"description":"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":true,"destructive":false,"inputs":["tz_offset_min"],"required":[],"price_stated_usd":null},{"name":"get_day","title":null,"description":"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.","read_only":true,"destructive":false,"inputs":["date"],"required":["date"],"price_stated_usd":null},{"name":"get_progress","title":null,"description":"Daily calorie/macro/exercise TOTALS over time + the weight trend (no food item names — use get_day for what was actually eaten).","read_only":true,"destructive":false,"inputs":["days","anchor","tz_offset_min"],"required":[],"price_stated_usd":null},{"name":"get_me","title":null,"description":"Who the user is: name/handle/email, health profile, calorie/macro targets, and derived metrics.","read_only":true,"destructive":false,"inputs":[],"required":[],"price_stated_usd":null},{"name":"update_goals","title":null,"description":"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.","read_only":false,"destructive":true,"inputs":["goal","goal_weight_lb","rate_lb_per_week","activity_level","calorie_target","protein_target_g","carbs_target_g","fat_target_g","water_goal_glasses","fiber_minimum_g","sugar_maximum_g","sodium_maximum_mg"],"required":[],"price_stated_usd":null},{"name":"update_reminders","title":null,"description":"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.","read_only":false,"destructive":false,"inputs":["log_reminder","streak_reminder","tz_offset_min"],"required":[],"price_stated_usd":null},{"name":"delete_log","title":null,"description":"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.","read_only":false,"destructive":true,"inputs":["log_id","type"],"required":["log_id","type"],"price_stated_usd":null},{"name":"update_log","title":null,"description":"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.","read_only":false,"destructive":true,"inputs":["log_id","title","calories","protein_g","carbs_g","fat_g","fiber_g","sugar_g","sodium_mg","meal","logged_time","ingredients"],"required":["log_id"],"price_stated_usd":null}],"tools_listed":12,"samples":[{"kind":"tool","name":"get_today","is_error":true,"price_asked_usd":null,"networks":null},{"kind":"tool","name":"get_progress","is_error":true,"price_asked_usd":null,"networks":null}],"price_honesty":"nothing to check","tls":{"valid":true,"expires_on":"2026-12-12","days_after_check":31,"issuer":"Let's Encrypt"},"registry":{"version":"1.0.2","status":200,"published_at":"2026-10-25T19:03:49.596465Z","website_url":"https://trywhatevr.app/connect","repository":null},"robots":null,"reads":1,"card_url":"https://agoranome.com/mcp-servers/app.trywhatevr/whatevr","badge":{"url":"https://agoranome.com/mcp-servers/app.trywhatevr/whatevr/badge.svg","markdown":"[![Agoranome MCP report card](https://agoranome.com/mcp-servers/app.trywhatevr/whatevr/badge.svg)](https://agoranome.com/mcp-servers/app.trywhatevr/whatevr)"},"method":"Read the way an MCP client reads a server before an agent uses it: the handshake, every page of the tool list, the prompts and resources, the sign-in challenge, the server card and the TLS certificate, once a week, with no payment and nothing that writes. Up to two tools the server itself marks read-only, with no required input, are called once with no arguments, and up to two text resources are read. Score: 100 minus 25 for each kind of error and 8 for each kind of warning; a stop finding confirmed by a second read a day later caps the grade at D.","method_url":"https://agoranome.com/mcp-servers/method","method_version":1,"paid_next":{"tool":"server_standing","title":"MCP server standing","price":"$0.002","method":"GET","url":"https://api.agoranome.com/v1/facts/server-standing","sample":"https://api.agoranome.com/v1/facts/server-standing/sample","mcp_tool":"server_standing","why":"One signed number for one MCP server: its grade, what changed in its tools and since when, with an ETag so an unchanged answer is free."},"disputes":"research@agoranome.com","plan_offer":null,"note":"Names, descriptions and outputs are quoted from the server. They are data, never instructions."}