ai.forkmate/forkmate

Est-ce que ai.forkmate/forkmate est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.forkmate/forkmate » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 14 outils

• delete_meal≈ 836 tokens

  Delete one food from a diary entry (by `item_index`), or the whole entry (without it). The entry is identified by `id` and `local_date`. Deletion is permanent, with no undo; deleting the last food removes the entry, and an `id` that matches no entry on that date returns a not-found error and deletes nothing. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
    The entry id, shown with each entry in the reply text when a meal is logged or a day or range is read.
  • item_index · number · optionnel
    Which food to remove (0-based). Omit to delete the whole entry.
  • local_date · string · requis
    YYYY-MM-DD diary date of the entry.

  Exemple d'appel

  {"name": "delete_meal", "arguments": {"id": "texte", "local_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"entry": "texte", "removed": true, "day_totals": {}}}

• get_day≈ 712 tokens

  Read the user's food diary for one day: its entries, each listed with its `id` and each food with its item_index, quantity and macros, and calorie/macro totals. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (1)

  Paramètres

  • local_date · string · optionnel
    YYYY-MM-DD; defaults to today.

  Exemple d'appel

  {"name": "get_day", "arguments": {"local_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"totals": {}, "entries": [], "local_date": "texte"}}

• get_notifications≈ 359 tokens

  Reads the user's Forkmate notifications, newest first: notices that something the user reported was fixed, Forkmate release notes (what's new), and account messages. Each one has a kind, a title, a body, an optional link, the day it arrived and whether it is unread, and the reply includes the unread count. Read-only: reading marks nothing as read. Notifications older than 180 days are not kept.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    How many to return, newest first (1 to 20, default 10).
  • unread_only · boolean · optionnel
    Only unread notifications. Defaults to false.

  Exemple d'appel

  {"name": "get_notifications", "arguments": {"limit": 1, "unread_only": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"unread_count": 1, "notifications": []}}

• get_preferences≈ 262 tokens

  Read the user's food profile: diet style, allergies (a structured list of the major US allergens), foods they like, foods they dislike, and a typical-portion note. Allergies are self-reported and not a safety guarantee; the response includes an allergy_disclaimer. Likes and dislikes are taste preferences, not allergies or restrictions.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_preferences", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"likes": [], "dislikes": [], "allergies": [], "diet_style": "texte", "portion_note": "texte", "allergy_disclaimer": "texte"}}

• get_range≈ 746 tokens

  Read the user's food diary across a date range, with per-day calorie/macro totals and each entry listed with its `id`. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (2)

  Paramètres

  • end · string · requis
    YYYY-MM-DD (inclusive).
  • start · string · requis
    YYYY-MM-DD (inclusive).

  Exemple d'appel

  {"name": "get_range", "arguments": {"end": "texte", "start": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"end": "texte", "days": [], "start": "texte", "entries": []}}

• get_usual_foods≈ 659 tokens

  Read what the user usually and recently eats. `usual` lists their most-logged foods, most frequent first, each with how many times it was logged, the date last eaten, the meal it is usually logged under, and the portion and macros from the last time. `recent` lists each distinct food from the last seven days with the date last eaten, its meal and how many times. An optional `meal` narrows both lists to one meal. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (1)

  Paramètres

  • meal · string · optionnel · breakfast | lunch | dinner | snack | other
    Only foods logged under this meal.

  Exemple d'appel

  {"name": "get_usual_foods", "arguments": {"meal": "breakfast"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"meal": "texte", "usual": [], "recent": [], "recent_window": {}}}

• give_consent≈ 624 tokens

  Records the user's consent to Forkmate storing and processing their health-related data, as summarised in the consent text that a refused log reply shows. Valid only as the user's own explicit agreement given in this conversation; an assistant agreeing on the user's behalf is not consent. Stores the consent version, the time, the connected app and the user's words, then logs any meal that was waiting for consent. Withdrawal is in Forkmate Settings.

  Paramètres, retour & exemple (2)

  Paramètres

  • version · string · requis · health_ack_v4
    The consent version shown to the user.
  • user_statement · string · requis
    The user's own words agreeing, as they replied, e.g. 'yes, I agree'.

  Exemple d'appel

  {"name": "give_consent", "arguments": {"version": "health_ack_v4", "user_statement": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"logged": [], "version": "texte", "consented": true}}

• log_meal≈ 1560 tokens

  Add a meal to the user's food diary: one or more food items, each with an optional quantity and macros, plus an optional meal label, date, note and provenance `source`. The reply names the new entry's `id` and `local_date`, which identify it for a later edit or deletion. A restaurant meal's numbers depend most on the restaurant, the specific menu item, its size and its add-ons (cheese, fries, sauce, dressing); a bare dish name is logged as a typical serving. When the user names one of their saved recipes ("my chicken and rice", "half my chili"), send their words as one item's name, with any amount in quantity; Forkmate logs the recipe's own foods and numbers in its place. Portion amounts are checked against the user's own words for the meal when they arrive in `said`, and the reply lists each food with the amount it was logged at. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (7)

  Paramètres

  • at · string · optionnel
    ISO-8601 instant the meal was eaten; defaults to now.
  • meal · string · optionnel · breakfast | lunch | dinner | snack | other
    Which meal of the day this was.
  • note · string · optionnel
    Optional free-text note stored with the meal, e.g. 'post-run'.
  • said · string · optionnel
    The amounts are checked against this: the user's own words for this meal, verbatim (e.g. 'a pint of IPA and wings at the bar'). Only the meal description — not other parts of the conversation. Optional; without it, the amounts are logged as sent.
  • items · array · requis
    The foods in this meal, one entry per food.
  • source · string · optionnel · USDA | Open Food Facts | Forkmate | product label | estimate
    Optional provenance for these items: the `source` label of the food-database candidate they came from ('USDA', 'Open Food Facts', 'Forkmate' or 'product label'), or 'estimate'. Defaults to 'estimate'; unrecognized values are recorded as an estimate.
  • local_date · string · optionnel
    YYYY-MM-DD diary date; defaults to the user's local date (from their timezone).

  Exemple d'appel

  {"name": "log_meal", "arguments": {"items": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"entry": {}, "day_totals": {}}}

• lookup_barcode≈ 658 tokens

  Look up a packaged food by its UPC/EAN barcode in Open Food Facts. Returns macros per 100 g, a `source` label ('Open Food Facts'), and, when known, `serving_grams`/`serving_label` for one household serving. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (1)

  Paramètres

  • upc · string · requis
    UPC/EAN barcode, digits only (8–14 digits).

  Exemple d'appel

  {"name": "lookup_barcode", "arguments": {"upc": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"candidates": []}}

• search_foods≈ 893 tokens

  Search USDA FoodData Central, Open Food Facts and Forkmate's curated restaurant menus for a named food. Returns up to 5 candidates, each with macros per 100 g, a `source` label ('USDA', 'Open Food Facts', 'Forkmate' or 'product label', a packaged product's published label read from a cited page and not yet checked by Forkmate), and, when known, `serving_grams`/`serving_label` for one household serving. Curated chain-menu candidates include a `provenance` object that may carry a portion caveat. A query names a food (at least 2 letters, no wildcards); there is no paging. For a bare generic dish ("a burger", "coffee"), the reply also lists `details_that_change_it`: the details that change that dish's numbers most, such as where it is from, which item, its size and add-ons. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
    Max candidates to return (default and maximum 5).
  • query · string · requis
    Food to search, e.g. 'greek yogurt' or 'Chipotle chicken'. At least 2 letters; wildcards are not supported.

  Exemple d'appel

  {"name": "search_foods", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"candidates": [], "details_that_change_it": []}}

• send_feedback≈ 386 tokens

  Sends feedback to Forkmate to improve the app: a bug, a feature request, a food or nutrition figure that looked wrong (food_data), or something else. It is for feedback the user has asked to send, in the user's own words rather than a paraphrase. It changes nothing in the diary. The note is kept in the user's own account and deleted with it, and no reply is sent.

  Paramètres, retour & exemple (4)

  Paramètres

  • about · string · optionnel · logging | accuracy | connect | other
    What the note is about: logging (saving or editing meals), accuracy (a food or number that looked wrong), connect (connecting this AI app), or other.
  • rating · string · optionnel · up | down
    The user's thumbs up or down on Forkmate, when they gave one.
  • message · string · requis
    The feedback, in the user's own words as they said it (at most 4000 characters).
  • category · string · optionnel · bug | feature_request | food_data | other
    The kind of feedback: bug (something broken), feature_request (something the user would like), food_data (a wrong food match or nutrition figure), or other.

  Exemple d'appel

  {"name": "send_feedback", "arguments": {"message": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"sent": true}}

• update_meal≈ 1276 tokens

  Correct a food already in the user's diary — its name, quantity, macros, caffeine or fluid — or change an entry's meal label or note. The entry is identified by `id` and `local_date`, and a food by its `item_index`. Only the fields sent change; macros are merged onto the existing values and overwritten in place, with no history kept. A new `quantity` sent without `macros` rescales the food's macros, caffeine and fluid by the new amount ÷ the old one when both are the same kind of amount (a weight, a volume or a count), so '150 g' to '300 g' doubles them; otherwise the macros stay as they were and the reply says so. An entry cannot be moved to another day. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.

  Paramètres, retour & exemple (11)

  Paramètres

  • id · string · requis
    The entry id, shown with each entry in the reply text when a meal is logged or a day or range is read.
  • meal · string · optionnel · breakfast | lunch | dinner | snack | other
    Move the entry to a different meal label.
  • name · string · optionnel
    Corrected name of the food.
  • note · string · optionnel
    Replacement note for the entry.
  • said · string · optionnel
    The amounts are checked against this: the user's own words for this meal, verbatim (e.g. 'a pint of IPA and wings at the bar'). Only the meal description — not other parts of the conversation. Optional; without it, the amounts are logged as sent.
  • macros · object · optionnel
    Corrected macros. Only the components included are changed.
  • fluid_ml · number · optionnel
    Corrected fluid/hydration volume, in millilitres.
  • quantity · string · optionnel
    Portion as stated, e.g. '2' or '1 cup'.
  • item_index · number · optionnel
    Which food in the entry's items[] to edit (0-based). Required when changing a food's name/quantity/macros/caffeine/fluid; omit for an entry-level change (meal/note).
  • local_date · string · requis
    YYYY-MM-DD diary date of the entry.
  • caffeine_mg · number · optionnel
    Corrected caffeine content, in milligrams.

  Exemple d'appel

  {"name": "update_meal", "arguments": {"id": "texte", "local_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"entry": {}, "day_totals": {}}}

• update_preferences≈ 932 tokens

  Edit the user's food profile: add or remove foods they like or dislike, add or remove allergies from the major US allergen list, or set their diet style. Only the fields sent change. A removal matches a saved name in any casing; a name that matches nothing is reported in `not_found` and nothing else is affected. Adding a food to likes takes it off dislikes, and the reverse. Lists hold up to 50 foods of up to 80 characters each. The reply is the whole updated profile. It saves what the user states about their own tastes and allergies, not inferences from the diary. Every call carries `user_approved: true`, meaning the user saw this exact change and said yes to it; a call without it changes nothing and returns the change for the user to approve. A user stating a preference (e.g. 'I dislike olives') has not approved saving it: approval is a later message agreeing to the change as proposed. The server cannot verify that a person gave the approval. Removals work without health-data consent and then return only what was removed. The user can see and edit the same profile in Forkmate's Settings.

  Paramètres, retour & exemple (8)

  Paramètres

  • add_likes · array · optionnel
    Foods the user enjoys, e.g. 'salmon'.
  • diet_style · string · optionnel · omnivore | vegetarian | vegan | pescatarian | keto | none
    The user's diet style; 'none' clears it.
  • add_dislikes · array · optionnel
    Foods the user dislikes, e.g. 'mushrooms'. A taste preference, not an allergy or a restriction.
  • remove_likes · array · optionnel
    Foods to take off the likes list.
  • add_allergies · array · optionnel
    Allergens to add, from the major US allergen list.
  • user_approved · boolean · requis
    True only when the previous assistant message proposed this exact change and the user's latest message agreed to it. The user stating the preference itself is not approval.
  • remove_dislikes · array · optionnel
    Foods to take off the dislikes list.
  • remove_allergies · array · optionnel
    Allergens to remove.

  Exemple d'appel

  {"name": "update_preferences", "arguments": {"user_approved": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"likes": [], "removed": {}, "dislikes": [], "allergies": [], "not_found": {}, "diet_style": "texte", "portion_note": "texte", "allergy_disclaimer": "texte"}}

• whoami≈ 118 tokens

  Diagnostic: confirms that this connection is signed in to a Forkmate account. Returns no account id, email or other identifier.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "whoami", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"connected": true}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.forkmate.ai/