Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Fitatu 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.
100/100
trust score
28
downloads a day
local
runs on your machine
223
downloads in 30d
What it does
Your Fitatu food diary as tools for AI agents: read a day, check calories and macros left against your goals, log meals by name or barcode, fix or remove entries with a preview, set calorie and macro goals, keep your own products from a nutrition label, and track weight, water, body measurements and workouts. 47 tools (26 read-only), with read-only and demo modes; runs over stdio or HTTP with a token. Works on free and Premium accounts; features that the Fitatu app reserves for Premium stay Premium. Install: uvx --from "fitatu-api[mcp]" fitatu-mcp (log in once with: uvx fitatu-api login). Unofficial: not affiliated with Fitatu.
Quickstart
Run once first — the server needs this before it answers:
uvx fitatu-api login# 1 — add it to Claude Code
claude mcp add --scope user fitatu-mcp '--' uvx --from 'fitatu-api[mcp]' fitatu-mcp
# 2 — ask your agent for something these tools do
# get_today, get_day, get_targets and 44 more
Fitatu costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Fitatu as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Run once first: uvx fitatu-api login. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user fitatu-mcp '--' uvx --from 'fitatu-api[mcp]' fitatu-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take FITATU_SESSION (Session file written by `fitatu-api login`; default ~/.fitatu/session.json.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
47 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.
Today's date in the user's time zone: date (YYYY-MM-DD), timezone and weekday.
No parameter schema on file.
Read one diary day: per meal its meal_key (the slot other tools take), meal_name (the name the user gave it) and every logged food (row_id, food_type, product_id or recipe_id, name, measure_id…
No parameter schema on file.
Read the user's daily goals for a day: energy in kcal, protein/fat/carbohydrate as grams and percent of energy, and BMR/TMR in kcal.
No parameter schema on file.
Read what the user's goals are computed from, for advice: height_cm, weight_kg (the current weight in the profile; a weigh-in logged for today updates it), start_weight_kg and target_weight_kg…
No parameter schema on file.
Read Fitatu's own summary of a date range, as the app's Summary tab shows it: nutrition (energy in kcal; protein, fat, carbohydrate, fiber, sugars, salt in g) counts every logged row…
No parameter schema on file.
Progress against the user's goals, day by day, for one day or a range of up to 62 days: per day and for energy, protein, fat and carbohydrate, logged (every row, planned or eaten…
No parameter schema on file.
The foods that gave the user the most of a nutrient over a date range, most first: name, amount (kcal for energy, g otherwise, summed over the range) and per100 (the food's own amount per 100 g…
No parameter schema on file.
A weekly or monthly report (or one of any range) in one call.
No parameter schema on file.
A shopping list for a range of up to 14 days, worked out from the rows planned in the diary and not ticked as eaten.
No parameter schema on file.
Search the Fitatu food catalog (Polish names work best).
No parameter schema on file.
Search the Fitatu recipe catalog for meal ideas, e.g. phrase 'kurczak' with max_energy_kcal 500 for a chicken dinner of at most 500 kcal, or diets ['vegan']…
No parameter schema on file.
Read one recipe in full, from the catalog or the user's own: name, servings (how many servings the ingredients make), ingredients for the whole recipe (food_id, food_type, quantity, measure_id, name…
No parameter schema on file.
Find the catalog product with a barcode (the EAN or UPC digits printed under the bars), or the user's own product with it (create_food's barcode).
No parameter schema on file.
List the measures a food can be logged in: measure_id, name (e.g. 'g', 'portion', 'piece'), weight_g or capacity_ml, energy_kcal and protein_g, fat_g…
No parameter schema on file.
List foods the user recently logged in a meal, most used first, in the same shape as search_food hits.
No parameter schema on file.
List the user's favourite products and recipes, in the same shape as search_food hits.
No parameter schema on file.
List the foods the user created, their own recipes (create_recipe) and products (create_food), in the same shape as search_food hits…
No parameter schema on file.
List logged body weights as {date, value, difference, direction}, newest first: value in the user's weight unit (kg unless changed in the app), difference from the previous entry…
No parameter schema on file.
Read how the user's body measurements changed over a period: per body_part (neck, chest, waist, stomach, hips, thigh, calf, biceps…
No parameter schema on file.
List the logged values of one body measurement as {date, value}, newest first: value in the user's size unit (cm unless changed in the app), fat_percentage in %.
No parameter schema on file.
Read how much water the user drank on a day (water_ml), the day's goal (target_ml) and the size of one glass in the user's settings (glass_ml); each is null when unknown.
No parameter schema on file.
Read the user's intermittent fasting (post przerywany) for a range of up to 62 days: days lists each day with fasting, its eating_periods (when the user ate…
No parameter schema on file.
Read the habits the user took up in the app (e.g. drinking water every day): per habit its habit_id, name, length_days (how long it runs), days_done and checked_days (the days ticked)…
No parameter schema on file.
List the days the app's summary marks as good days (Fitatu's own rule decides which), oldest first, with their count.
No parameter schema on file.
Search the activity (workout) catalog, e.g. 'bieganie' (running) or 'rower' (cycling).
No parameter schema on file.
Show what remove_items would delete, without deleting anything: would_remove lists each food row with what it is (meal, meal_name, row_id, name, food_type, food_id, measure_id, measure_name…
No parameter schema on file.
Log a catalog food in a meal; returns its row_id.
No parameter schema on file.
Log several catalog foods in one meal with one write, e.g. a whole breakfast.
No parameter schema on file.
Log a food that is not in the catalog, by name and the nutrition of the whole amount eaten; returns its row_id.
No parameter schema on file.
Change a logged food row: its quantity (in the row's own measure, see measure_name and measure_quantity in get_day) and/or eaten.
No parameter schema on file.
Move a logged food row to another meal and/or day.
No parameter schema on file.
Copy the food rows of a meal, or only row_ids of it, to another meal and/or day in one write, e.g. 'the same breakfast as yesterday' or 'plan this lunch for tomorrow'.
No parameter schema on file.
Delete logged food rows from a day by row_id (meals[].items[].row_id in get_day).
No parameter schema on file.
Save the user's body weight for a day in kg, replacing a weight already saved for that day; other body measurements of that day are kept.
No parameter schema on file.
Save body measurements for a day: sizes in the user's size unit (cm unless changed in the app), fat_percentage in %.
No parameter schema on file.
Set the total water drunk on a day in ml.
No parameter schema on file.
Change the user's daily goals from today on; earlier days keep theirs.
No parameter schema on file.
Replace the user's note for a diary day (get_day's note) with note; an empty note deletes it.
No parameter schema on file.
Log a workout from the activity catalog; returns its row_id.
No parameter schema on file.
Delete a logged activity by row_id (activities[].row_id in get_day, or from add_activity).
No parameter schema on file.
Add a catalog food to the user's favourites, or remove it with favorite false.
No parameter schema on file.
Save a private recipe in the user's own foods from catalog products, e.g. their usual smoothie, so it can be logged as one food.
No parameter schema on file.
Change one of the user's own private recipes (create_recipe's recipe_id or a get_my_foods RECIPE hit's food_id): its name, ingredients (the whole new list…
No parameter schema on file.
Delete one of the user's own private recipes: create_recipe's recipe_id or a get_my_foods RECIPE hit's food_id.
No parameter schema on file.
Save a product in the user's own foods from its nutrition label, e.g. a bar the catalog does not have, to log it by weight or by its servings.
No parameter schema on file.
Change one of the user's own products (create_food's food_id or a get_my_foods PRODUCT hit's food_id): any value create_food takes but unit; what is not given stays as it is…
No parameter schema on file.
Delete one of the user's own products: create_food's food_id or a get_my_foods PRODUCT hit's food_id.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Fitatu 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: —
ATrust score 100 / 100
Release 0.6.0 · scanned 16 Oct 2026
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 score100
Findings4 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest2e5dc017977d62adc001251fc67d8a734fdc9ce4892d20528aee379a46bc6028
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digest2e5dc017977d62ad
Scanned2026-10-16
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.6.0. Pin a release below and the command asks for exactly that one.
0.6.0
15 Oct 2026
latestNo release note was published with this version.
0.5.1
15 Oct 2026
No release note was published with this version.
0.5.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Fitatu 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.