forkmate

endpoint

https://mcp.forkmate.ai/

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is forkmate live?

Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.

Is forkmate free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does forkmate have?

14 tools: whoami, get_day, get_range, update_preferences, get_usual_foods, log_meal, give_consent, send_feedback, ….

Is forkmate safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• whoami reads auth-required 40d ago

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

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• get_day reads auth-required 40d ago

  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.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "local_date": {
        "type": "string",
        "description": "YYYY-MM-DD; defaults to today."
      }
    }
  }

  arguments 9 lines copy
• get_range reads auth-required 40d ago

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "start",
      "end"
    ],
    "properties": {
      "end": {
        "type": "string",
        "description": "YYYY-MM-DD (inclusive)."
      },
      "start": {
        "type": "string",
        "description": "YYYY-MM-DD (inclusive)."
      }
    }
  }

  arguments 17 lines copy
• update_preferences changes data auth-required never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889

  {
    "type": "object",
    "required": [
      "user_approved"
    ],
    "properties": {
      "add_likes": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Foods the user enjoys, e.g. 'salmon'."
      },
      "diet_style": {
        "enum": [
          "omnivore",
          "vegetarian",
          "vegan",
          "pescatarian",
          "keto",
          "none"
        ],
        "type": "string",
        "description": "The user's diet style; 'none' clears it."
      },
      "add_dislikes": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Foods the user dislikes, e.g. 'mushrooms'. A taste preference, not an allergy or a restriction."
      },
      "remove_likes": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Foods to take off the likes list."
      },
      "add_allergies": {
        "type": "array",
        "items": {
          "enum": [
            "milk",
            "eggs",
            "fish",
            "shellfish",
            "tree_nuts",
            "peanuts",
            "wheat",
            "soy",
            "sesame"
          ],
          "type": "string"
        },
        "description": "Allergens to add, from the major US allergen list."
      },
      "user_approved": {
        "type": "boolean",
        "description": "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": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Foods to take off the dislikes list."
      },
      "remove_allergies": {
        "type": "array",
        "items": {
          "enum": [
            "milk",
            "eggs",
            "fish",
            "shellfish",
            "tree_nuts",
            "peanuts",
            "wheat",
            "soy",
            "sesame"
          ],
          "type": "string"
        },
        "description": "Allergens to remove."
      }
    },
    "additionalProperties": false
  }

  arguments 89 lines copy
• get_usual_foods reads auth-required never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "properties": {
      "meal": {
        "enum": [
          "breakfast",
          "lunch",
          "dinner",
          "snack",
          "other"
        ],
        "type": "string",
        "description": "Only foods logged under this meal."
      }
    },
    "additionalProperties": false
  }

  arguments 17 lines copy
• log_meal changes data auth-required never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102

  {
    "type": "object",
    "required": [
      "items"
    ],
    "properties": {
      "at": {
        "type": "string",
        "description": "ISO-8601 instant the meal was eaten; defaults to now."
      },
      "meal": {
        "enum": [
          "breakfast",
          "lunch",
          "dinner",
          "snack",
          "other"
        ],
        "type": "string",
        "description": "Which meal of the day this was."
      },
      "note": {
        "type": "string",
        "description": "Optional free-text note stored with the meal, e.g. 'post-run'."
      },
      "said": {
        "type": "string",
        "maxLength": 300,
        "description": "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": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "name"
          ],
          "properties": {
            "name": {
              "type": "string",
              "description": "What the food is, e.g. 'scrambled eggs' or 'Greek yogurt, plain'."
            },
            "macros": {
              "type": "object",
              "properties": {
                "kcal": {
                  "type": "number",
                  "description": "Energy for the whole portion eaten, in kilocalories (not per 100 g)."
                },
                "fat_g": {
                  "type": "number",
                  "description": "Total fat for the whole portion eaten, in grams."
                },
                "carb_g": {
                  "type": "number",
                  "description": "Total carbohydrate for the whole portion eaten, in grams."
                },
                "protein_g": {
                  "type": "number",
                  "description": "Protein for the whole portion eaten, in grams."
                }
              },
              "description": "Estimated nutrition for the portion eaten. Omitted fields are looked up from the food databases. Without this object, kcal (or calories), protein_g, carb_g (or carbs_g) and fat_g set on the item itself are read as these macros."
            },
            "barcode": {
              "type": "string",
              "description": "The package's UPC/EAN barcode, when the food came from a barcode lookup."
            },
            "fluid_ml": {
              "type": "number",
              "description": "Optional fluid/hydration volume of this item, in millilitres (e.g. 240 for an 8 oz cup)."
            },
            "quantity": {
              "type": "string",
              "description": "Portion as a display label, e.g. '3', '1 cup' or '2 × 1 frank (96 g)'. Display only: the server stores macros exactly as sent and does not re-scale them."
            },
            "caffeine_mg": {
              "type": "number",
              "description": "Optional caffeine content of this item, in milligrams (e.g. ~95 for an 8 oz brewed coffee). If you omit it, Forkmate fills it from the label or its reference table when it knows the drink."
            }
          }
        },
        "minItems": 1,
        "description": "The foods in this meal, one entry per food."
      },
      "source": {
        "enum": [
          "USDA",
          "Open Food Facts",
          "Forkmate",
          "product label",
          "estimate"
        ],
        "type": "string",
        "description": "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": {
        "type": "string",
        "description": "YYYY-MM-DD diary date; defaults to the user's local date (from their timezone)."
      }
    }
  }

  arguments 102 lines copy
• give_consent auth-required never probed

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "required": [
      "user_statement",
      "version"
    ],
    "properties": {
      "version": {
        "enum": [
          "health_ack_v5"
        ],
        "type": "string",
        "description": "The consent version shown to the user."
      },
      "user_statement": {
        "type": "string",
        "maxLength": 280,
        "description": "The user's own words agreeing, as they replied, e.g. 'yes, I agree'."
      }
    },
    "additionalProperties": false
  }

  arguments 22 lines copy
• send_feedback auth-required never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142

  {
    "type": "object",
    "required": [
      "message"
    ],
    "properties": {
      "about": {
        "enum": [
          "logging",
          "accuracy",
          "connect",
          "other"
        ],
        "type": "string",
        "description": "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": {
        "enum": [
          "up",
          "down"
        ],
        "type": "string",
        "description": "The user's thumbs up or down on Forkmate, when they gave one."
      },
      "message": {
        "type": "string",
        "maxLength": 4000,
        "description": "The feedback, in the user's own words as they said it (at most 4000 characters)."
      },
      "category": {
        "enum": [
          "bug",
          "feature_request",
          "food_data",
          "other"
        ],
        "type": "string",
        "description": "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."
      }
    },
    "additionalProperties": false
  }

  arguments 42 lines copy
• get_preferences reads auth-required 40d ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• update_meal changes data auth-required never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879

  {
    "type": "object",
    "required": [
      "id",
      "local_date"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The entry id, shown with each entry in the reply text when a meal is logged or a day or range is read."
      },
      "meal": {
        "enum": [
          "breakfast",
          "lunch",
          "dinner",
          "snack",
          "other"
        ],
        "type": "string",
        "description": "Move the entry to a different meal label."
      },
      "name": {
        "type": "string",
        "description": "Corrected name of the food."
      },
      "note": {
        "type": "string",
        "description": "Replacement note for the entry."
      },
      "said": {
        "type": "string",
        "maxLength": 300,
        "description": "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": {
        "type": "object",
        "properties": {
          "kcal": {
            "type": "number",
            "description": "Corrected energy for the whole portion, in kilocalories."
          },
          "fat_g": {
            "type": "number",
            "description": "Corrected total fat for the whole portion, in grams."
          },
          "carb_g": {
            "type": "number",
            "description": "Corrected total carbohydrate for the whole portion, in grams."
          },
          "protein_g": {
            "type": "number",
            "description": "Corrected protein for the whole portion, in grams."
          }
        },
        "description": "Corrected macros. Only the components included are changed."
      },
      "fluid_ml": {
        "type": "number",
        "description": "Corrected fluid/hydration volume, in millilitres."
      },
      "quantity": {
        "type": "string",
        "description": "Portion as stated, e.g. '2' or '1 cup'."
      },
      "item_index": {
        "type": "number",
        "description": "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": {
        "type": "string",
        "description": "YYYY-MM-DD diary date of the entry."
      },
      "caffeine_mg": {
        "type": "number",
        "description": "Corrected caffeine content, in milligrams."
      }
    }
  }

  arguments 79 lines copy
• delete_meal changes data auth-required never probed

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "id",
      "local_date"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "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": {
        "type": "number",
        "description": "Which food to remove (0-based). Omit to delete the whole entry."
      },
      "local_date": {
        "type": "string",
        "description": "YYYY-MM-DD diary date of the entry."
      }
    }
  }

  arguments 21 lines copy
• search_foods reads auth-required 40d ago

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "number",
        "description": "Max candidates to return (default and maximum 5)."
      },
      "query": {
        "type": "string",
        "description": "Food to search, e.g. 'greek yogurt' or 'Chipotle chicken'. At least 2 letters; wildcards are not supported."
      }
    },
    "additionalProperties": false
  }

  arguments 17 lines copy
• lookup_barcode reads auth-required 40d ago

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "upc"
    ],
    "properties": {
      "upc": {
        "type": "string",
        "description": "UPC/EAN barcode, digits only (8–14 digits)."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• get_notifications auth-required never probed

  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.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 20,
        "minimum": 1,
        "description": "How many to return, newest first (1 to 20, default 10)."
      },
      "unread_only": {
        "type": "boolean",
        "description": "Only unread notifications. Defaults to false."
      }
    },
    "additionalProperties": false
  }

  arguments 16 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.