← Registry

Productivity

trywhatevr.app

Logs food, water, exercise, and weight entries and returns daily calorie, macro, water, streak, and food-log summaries.

1 endpoint9 known toolsFirst detected October 26, 2026Last detected October 26, 2026

ENDPOINT 1

https://api.trywhatevr.app/mcp

No auth detected

MCP server metadata

Name
whatevr
Version
1.0.0
Capabilities
tools
Server instructions

Log food, water, exercise, and weigh-ins to the user's whatevr account, and read their day, progress, and profile. Every tool call needs the user's API token in the Authorization header (Bearer wtvr_live_…) — they create one in the whatevr app under Settings → API Access. Clients whose connector setup can't send headers can put the token in the connect URL instead: POST /mcp/<token>. Timestamps are bare-local (YYYY-MM-DDThh:mm:ss, no zone); when logging 'now', pass tz_offset_min (the user's JS getTimezoneOffset(), minutes behind UTC) so entries land on their calendar day. Prefer log_anything for anything said in plain words — it runs the same parser as the app's voice logging.

Known tools 9

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.

Inferred read-only
log_exercise

Log structured exercise with a known calorie burn.

Inferred read-only
log_weight

Log a weigh-in in pounds.

Inferred read-only
log_water

Log water — glasses (8 fl oz each) or an exact amount_fl_oz.

Inferred read-only
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).

Inferred read-only
get_day

Everything logged on a specific day, INCLUDING each food item's name and nutrition (same shape as get_today).

Inferred read-only
get_progress

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

Inferred read-only
get_me

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

Potential side effects
update_log

Correct an existing FOOD log: title, nutrition numbers, the ingredient list, meal, or time-of-day.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.whatevr]
url = "https://api.trywhatevr.app/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "whatevr": {
      "type": "http",
      "url": "https://api.trywhatevr.app/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: whatevr
Remote MCP URL: https://api.trywhatevr.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "whatevr": {
      "url": "https://api.trywhatevr.app/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "whatevr": {
      "type": "http",
      "url": "https://api.trywhatevr.app/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "whatevr",
  "transport": "streamable-http",
  "url": "https://api.trywhatevr.app/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.