Skip to content

MCP servers › io.github.Jezue › fitatu-api

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.Jezue/fitatu-api

Unofficial Fitatu calorie counter: read and log food, weight, water and workouts. — the publisher's description

8 of 8 record checks metRead-only · tools listed 2026-10-23Topic: science-health-and-education · AI-classifiedversion 0.6.0PythonMITstandard input/output47 tools

Summary

io.github.Jezue/fitatu-api is a local MCP server listed in the official MCP registry at version 0.6.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 47 tools, 0 resources and 3 prompts.

Record checks

8 of 8 record checks met · 1 does not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #14,745 of 15,112 packages by monthly downloads, tied with 367 others
  • #1,801 of 22,952 repositories by GitHub stars, tied with 44 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
local package
Transport
standard input/output
Package
PyPI · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Tools
47
Described as changing data
14 of 47 toolsAI-classified
Topic
science-health-and-educationAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 14 tools are described as changing something (add_food, add_foods, add_custom_item, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.6.0, published 2026-10-15 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-14 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-10-14 to 2026-10-15; 3 in the 90 days before the 2026-10-23 snapshot.
Most recent 3 versions
  • 0.6.0 · 2026-10-15
  • 0.5.1 · 2026-10-15
  • 0.5.0 · 2026-10-14
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.6.0 (published 2026-10-15).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
47tools
0resources
3prompts

14 of 47 tools are described as changing something (creating, editing, deleting, sending or running). For 7 the reading was uncertain, so no mark is shown.

  • get_todayon 12 other serversreads or searches

    “Today's date in the user's time zone: date (YYYY-MM-DD), timezone and weekday.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_dayon 5 other serversreads or searches

    “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, measu…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_targetson 2 other serversreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_profileon 124 other serversreads or searches

    “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, bmi (…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_range_summaryreads or searches

    “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, ticked as eaten…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • from_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_progresson 5 other serversreads or searches

    “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; null when nothing i…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • from_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_top_foodsreads or searches

    “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; null…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • from_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • nutrientstring“What to rank the foods by.”
    • limitinteger“Maximum number of hits.”
  • get_reporton 57 other serversreads or searches

    “A weekly or monthly report (or one of any range) in one call.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • from_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_shopping_listreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • from_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • search_foodon 5 other serversreads or searches

    “Search the Fitatu food catalog (Polish names work best).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • phrasestringrequired“What to look for, e.g.”
    • limitinteger“Maximum number of hits.”
    • localestring“Another country's catalog, e.g.”
  • search_recipeson 29 other serversreads or searches

    “Search the Fitatu recipe catalog for meal ideas, e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    8 inputs
    • phrasestring“Words to look for, e.g.”
    • max_energy_kcalnumber“Only recipes of at most this many kcal per portion.”
    • min_protein_ginteger“Only recipes with at least this many g of protein per portion.”
    • max_carbohydrate_ginteger“Only recipes with at most this many g of carbohydrate per portion.”
    • max_cooking_timeinteger“Only recipes with a cooking_time of at most 10 or 30 minutes, the catalog's two time filters.”
    • dietsarray“Diets every hit must fit, e.g.”
    • mealstring“Only recipes the catalog suggests for this meal type (dinner is obiad, supper kolacja).”
    • limitinteger“Maximum number of hits.”
  • get_recipeon 30 other serversreads or searches

    “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,…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • recipe_idintegerrequired“food_id of a RECIPE hit (search_recipes, search_food, get_my_foods, get_favorite_foods, get_recent_foods), create_recipe's recipe_id or a get_day row's recipe_…”
Show 35 more tools
  • find_by_barcodereads or searches

    “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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • barcodestringrequired“The 8 to 14 digits, without spaces, e.g.”
  • get_food_measuresreads or searches

    “List the measures a food can be logged in: measure_id, name (e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 2 required
    • food_idintegerrequired“food_id of a search_food, search_recipes, find_by_barcode, get_recent_foods, get_favorite_foods or get_my_foods hit, create_food's food_id (PRODUCT), create_re…”
    • food_typestringrequired“type of that search hit, or the get_day row's food_type.”
  • get_recent_foodsreads or searches

    “List foods the user recently logged in a meal, most used first, in the same shape as search_food hits.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • mealstringrequired“Meal slot.”
    • limitinteger“Maximum number of hits.”
  • get_favorite_foodsreads or searches

    “List the user's favourite products and recipes, in the same shape as search_food hits.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger“Maximum number of hits.”
  • get_my_foodsreads or searches

    “List the foods the user created, their own recipes (create_recipe) and products (create_food), in the same shape as search_food hits: a RECIPE hit's food_id is what update_recipe and delete_recipe ta…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • phrasestring“Words of the name; omit it for all of them.”
    • limitinteger“Maximum number of hits.”
  • get_weight_historyreads or searches

    “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, direction the weigh…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • from_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • limitinteger“Maximum number of entries.”
  • get_body_measurementsreads or searches

    “Read how the user's body measurements changed over a period: per body_part (neck, chest, waist, stomach, hips, thigh, calf, biceps, fat_percentage) the first and last value of the period (start_value…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • from_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_measurement_historyreads or searches

    “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 %.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • body_partstringrequired“The measurement, e.g.”
    • from_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • limitinteger“Maximum number of entries.”
  • get_wateron 1 other serverreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_fastingreads or searches

    “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, from and to as times of day) next to expe…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • from_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • get_habitsreads or searches

    “Read the habits the user took up in the app (e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_good_daysreads or searches

    “List the days the app's summary marks as good days (Fitatu's own rule decides which), oldest first, with their count.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • from_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • to_datestring“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • search_activityon 2 other serversreads or searches

    “Search the activity (workout) catalog, e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • phrasestringrequired“Activity name, e.g.”
    • limitinteger“Maximum number of hits.”
  • preview_removalreads or searches

    “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, measure_…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • row_idsarrayrequired“row_ids from get_day.”
  • add_foodcreates or changes datadescribed as changing data

    “Log a catalog food in a meal; returns its row_id.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    9 inputs, 5 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • mealstringrequired“Meal slot.”
    • food_idintegerrequired“food_id of a search_food, search_recipes, find_by_barcode, get_recent_foods, get_favorite_foods or get_my_foods hit, create_food's food_id (PRODUCT), create_re…”
    • food_typestringrequired“type of that search hit, or the get_day row's food_type.”
    • quantitynumberrequired“Grams or ml with unit, else how many of the measure.”
    • measure_idinteger“measure_id of this food, from its search hit or get_food_measures.”
    • unitstring“Products only: quantity is in g or ml.”
    • eatenboolean“true when the user ate or drank it or just asks to log it; false (the default) only when they plan ahead.”
    • row_idstring“Optional UUID version 1 for the new row; omit it to get a new id.”
  • add_foodscreates or changes datadescribed as changing data

    “Log several catalog foods in one meal with one write, e.g.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs, 3 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • mealstringrequired“Meal slot.”
    • itemsarrayrequired“The foods, each as add_food takes it.”
    • eatenboolean“Sets every row: true (the default) when the user ate them or just asks to log them; false only when they plan ahead.”
    • row_idstring“Optional UUID version 1 the rows' row_ids are derived from; omit it to get a new one.”
  • add_custom_itemcreates or changes datadescribed as changing data

    “Log a food that is not in the catalog, by name and the nutrition of the whole amount eaten; returns its row_id.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    9 inputs, 4 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • mealstringrequired“Meal slot.”
    • namestringrequired“What it was, e.g.”
    • energy_kcalnumberrequired“Energy in kcal.”
    • protein_gnumber“Protein in grams.”
    • fat_gnumber“Fat in grams.”
    • carbohydrate_gnumber“Carbohydrate in grams.”
    • eatenboolean“true when the user ate or drank it or just asks to log it; false (the default) only when they plan ahead.”
    • row_idstring“Optional UUID version 1 for the new row; omit it to get a new id.”
  • update_itemon 8 other serverscreates or changes datadescribed as changing data

    “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.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    4 inputs, 2 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • row_idstringrequired“row_id of a food row on that day, from get_day (meals[].items[].row_id).”
    • quantitynumber“New measure_quantity.”
    • eatenboolean“true for eaten, false for only planned.”
  • move_itemon 5 other serverscreates or changes datadescribed as changing data

    “Move a logged food row to another meal and/or day.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    4 inputs, 3 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • row_idstringrequired“row_id of a food row on that day, from get_day (meals[].items[].row_id).”
    • to_mealstringrequired“Meal to move it to.”
    • to_datestring“Day to move it to, as YYYY-MM-DD (default: the same day); when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
  • copy_mealcreates or changes datadescribed as changing data

    “Copy the food rows of a meal, or only row_ids of it, to another meal and/or day in one write, e.g.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    7 inputs, 3 required
    • from_datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • from_mealstringrequired“Meal to copy.”
    • to_datestringrequired“Day to copy to, as YYYY-MM-DD (from_date itself when to_meal differs); when the user says today, yesterday, this week or a weekday, call get_today and count fr…”
    • to_mealstring“Meal to copy into (default: from_meal).”
    • row_idsarray“Only these rows of from_meal (row_ids from get_day); omit it for the whole meal.”
    • eatenboolean“Sets every copy: true when the user ate it or just asks to log it, false when they plan ahead.”
    • row_idstring“Optional UUID version 1 the copies' row_ids are derived from; omit it to get a new one.”
  • remove_itemsdeletesdescribed as changing data

    “Delete logged food rows from a day by row_id (meals[].items[].row_id in get_day).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 2 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • row_idsarrayrequired“row_ids from get_day.”
    • dry_runboolean“Only report what would be deleted; preview_removal does it without a destructive call.”
  • log_weighton 1 other servercreates or changes datadescribed as changing data

    “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.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • weight_kgnumberrequired“Body weight in kg; convert pounds first (1 lb = 0.4536 kg).”
  • log_measurementscreates or changes datadescribed as changing data

    “Save body measurements for a day: sizes in the user's size unit (cm unless changed in the app), fat_percentage in %.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    10 inputs, 1 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • necknumber“Neck circumference.”
    • chestnumber“Chest circumference.”
    • waistnumber“Waist circumference.”
    • stomachnumber“Stomach circumference.”
    • hipsnumber“Hips circumference.”
    • thighnumber“Thigh circumference.”
    • calfnumber“Calf circumference.”
    • bicepsnumber“Biceps circumference.”
    • fat_percentagenumber“Body fat in %.”
  • set_watercreates or changes datadescribed as changing data

    “Set the total water drunk on a day in ml.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • water_mlintegerrequired“Total for the day in ml.”
  • set_targetscreates or changes datadescribed as changing data

    “Change the user's daily goals from today on; earlier days keep theirs.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    6 inputs
    • energy_kcalinteger“Daily calorie goal in kcal; makes the goal manual.”
    • protein_pctinteger“Protein's share of the energy goal in whole percent; with fat_pct and carbohydrate_pct, summing to 100.”
    • fat_pctinteger“Fat's share of the energy goal in whole percent (not body fat).”
    • carbohydrate_pctinteger“Carbohydrate's share of the energy goal in whole percent.”
    • automaticboolean“true: back to the goal Fitatu calculates.”
    • water_glass_mlinteger“Size of one glass in ml.”
  • set_noteon 2 other serverscreates or changes datadescribed as changing data

    “Replace the user's note for a diary day (get_day's note) with note; an empty note deletes it.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • notestringrequired“The whole new note, '' to delete it.”
  • add_activityon 2 other serverscreates or changes datadescribed as changing data

    “Log a workout from the activity catalog; returns its row_id.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs, 4 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • activity_idintegerrequired“activity_id from search_activity.”
    • minutesintegerrequired“Duration in minutes.”
    • energy_kcalintegerrequired“Energy burned in kcal.”
    • row_idstring“Optional UUID version 1 for the new row; omit it to get a new id.”
  • remove_activitydeletesdescribed as changing data

    “Delete a logged activity by row_id (activities[].row_id in get_day, or from add_activity).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • datestringrequired“Day as YYYY-MM-DD; when the user says today, yesterday, this week or a weekday, call get_today and count from its date.”
    • row_idstringrequired“row_id of an activity on that day.”
  • set_favorite

    “Add a catalog food to the user's favourites, or remove it with favorite false.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • food_idintegerrequired“food_id of a search_food, search_recipes, find_by_barcode, get_recent_foods, get_favorite_foods or get_my_foods hit, create_food's food_id (PRODUCT), create_re…”
    • food_typestringrequired“type of that search hit, or the get_day row's food_type.”
    • favoriteboolean“false to remove it from the favourites.”
  • create_recipeon 6 other servers

    “Save a private recipe in the user's own foods from catalog products, e.g.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    4 inputs, 2 required
    • namestringrequired“The recipe's name, e.g.”
    • ingredientsarrayrequired“The products in it, each as add_food takes it.”
    • servingsinteger“How many servings the ingredients make.”
    • descriptionstring“How to make it, as the app shows it.”
  • update_recipeon 5 other servers

    “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, each as create_recipe takes it and checked …”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    5 inputs, 1 required
    • recipe_idintegerrequired“Id of a recipe the user created.”
    • namestring“The new name.”
    • ingredientsarray“Every product of the recipe, each as add_food takes it; replaces the list.”
    • servingsinteger“How many servings the ingredients make.”
    • descriptionstring“How to make it, as the app shows it.”
  • delete_recipeon 4 other servers

    “Delete one of the user's own private recipes: create_recipe's recipe_id or a get_my_foods RECIPE hit's food_id.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • recipe_idintegerrequired“Id of a recipe the user created.”
  • create_food

    “Save a product in the user's own foods from its nutrition label, e.g.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    13 inputs, 5 required
    • namestringrequired“The product's name, e.g.”
    • energy_kcalnumberrequired“Energy in kcal, not kJ, in 100 g (100 ml for a drink), as the label gives it.”
    • protein_gnumberrequired“Protein in g in 100 g (100 ml for a drink), as the label gives it.”
    • fat_gnumberrequired“Fat in g in 100 g (100 ml for a drink), as the label gives it.”
    • carbohydrate_gnumberrequired“Carbohydrate in g in 100 g (100 ml for a drink), as the label gives it.”
    • brandstring“Its brand, if the label has one.”
    • sugars_gnumber“Of which sugars, in g; at most carbohydrate_g.”
    • fiber_gnumber“Fibre in g.”
    • salt_gnumber“Salt in g.”
    • saturated_fat_gnumber“Of which saturated fat, in g; at most fat_g.”
    • servingsarray“Its servings, each name once, e.g.”
    • barcodestring“The 8 to 14 digits under the bars.”
    • unitstring“ml for a drink whose label gives values per 100 ml.”
  • “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, and servings replaces th…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    13 inputs, 1 required
    • food_idintegerrequired“create_food's food_id, or a get_my_foods PRODUCT hit's food_id.”
    • namestring“The product's name, e.g.”
    • energy_kcalnumber“Energy in kcal, not kJ, in 100 g (100 ml for a drink), as the label gives it.”
    • protein_gnumber“Protein in g in 100 g (100 ml for a drink), as the label gives it.”
    • fat_gnumber“Fat in g in 100 g (100 ml for a drink), as the label gives it.”
    • carbohydrate_gnumber“Carbohydrate in g in 100 g (100 ml for a drink), as the label gives it.”
    • brandstring“Its brand, if the label has one.”
    • sugars_gnumber“Of which sugars, in g; at most carbohydrate_g.”
    • fiber_gnumber“Fibre in g.”
    • salt_gnumber“Salt in g.”
    • saturated_fat_gnumber“Of which saturated fat, in g; at most fat_g.”
    • servingsarray“Every serving of it, each name once; replaces the list.”
    • barcodestring“The 8 to 14 digits under the bars.”
  • “Delete one of the user's own products: create_food's food_id or a get_my_foods PRODUCT hit's food_id.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • food_idintegerrequired“create_food's food_id, or a get_my_foods PRODUCT hit's food_id.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 40 tools
Says what it returns
100% of 40 tools
States limits, defaults or errors
21% of 38 tools
Says when to use it
10% of 39 tools
Items covered per tool
2.4 of 4 on average

Counted from the listing

Parameters with a description
100% of 162
Tools with a description
100% of 47
Typical description length
482 characters

The tool set

Counted from the listing

Tools
47
Size of the list
about 28,128 tokens for an agent to load (characters ÷ 4)
Naming
47 of 47 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 40 of 47 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry
  • No config: the PyPI package declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.6.0
Latest stable
0.6.0
Status
current
Withdrawn
no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-fed2f328714bd21a4…
License
MIT

Source: the package registry · 2026-10-23.

Usage

Downloads
0 in the last month

Source: pypistats.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Version 0.6.0 on PyPIExists and can be installedmatchesPyPI · 2026-10-23
Repository github.com/Jezue/fitatu_libraryOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.Jezue
GitHub owner
a personal account (Jezue)
Repository
github.com/Jezue/fitatu_library
Stars
21
Repository age
181–365 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 8 record checks met · 1 does not apply

  • #14,745 of 15,112 packages by monthly downloads, tied with 367 others
  • #1,801 of 22,952 repositories by GitHub stars, tied with 44 others
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Jezue/fitatu-api

Answered from the data above

Is io.github.Jezue/fitatu-api safe to install?

We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 14 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.Jezue/fitatu-api been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.Jezue/fitatu-api do?

It lists 47 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and delete. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Jezue/fitatu-api change or delete data?

14 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.Jezue/fitatu-api publish a security policy?

Yes: its repository has a public security policy (github.com/jezue/fitatu_library/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.6.0, the latest stable release on PyPI.

Where is the source code of io.github.Jezue/fitatu-api?

In github.com/Jezue/fitatu_library, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “science-health-and-education” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 9
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
Does not apply to this server · 5
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 2,634 msConnected after 0 redirects.
  3. Read the inventory: 47 tools, 0 resources, 3 prompts.
  4. 3,410 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, tools
our test · 2026-10-23
Transport
standard input/output
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-23
Integrity hash
declared (sha256)
package registry · 2026-10-23
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-10-23
Popularity
0 downloads a month
package registry · 2026-10-23
Publisher signals
owner: a personal account · repository age: 181–365 days · stars: 10–99
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
your machine
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Jezue/fitatu-api: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Jezue/fitatu-api

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 8 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Jezue/fitatu-api)](https://protocolprobe.com/mcp/servers/io.github.Jezue/fitatu-api)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology