foodose MCP server

Which servers in the official MCP registry are foodose's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to foodose

Whose server it is

Registry nameco.foodose/glp1-nutritionverified in the MCP registry

The registry name sits under foodose.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools4
Server calls itselffoodose
Server version1.0.0
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 114 ms.

Tools it offers4 tools · read 2026-10-13

calculate_glp1_target
Daily calorie, protein, carbohydrate, fat and fibre targets for someone taking a GLP-1 receptor agonist, plus the appetite ceiling: a dose aware estimate of the most they are likely to manage in a day. Use it for anyone taking or…
get_appetite_ceiling
The appetite suppression factor foodose models for a given medication and dose, with the evidence it is anchored to and the licensed doses for that drug. This is the site's original data: the estimate of how much less a person eats at a…
search_foods
Per 100 g nutrition for the foods foodose uses, each with a realistic serving size and a GLP-1 tolerance rating describing how well it tends to sit when appetite is low. Free to use with attribution.
search_recipes
Published GLP-1 recipes with per serving calories and protein, every ingredient traceable to a USDA FoodData Central record. Useful when someone asks what to actually eat, rather than what their targets are.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "glp1-nutrition": {
      "type": "http",
      "url": "https://www.foodose.co/mcp"
    }
  }
}

OpenAPI spec

2 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.