mcpbeat Sign in

Dieta.ai MCP Server

answering

Dieta.ai is answering right now. Last checked 7 min ago. It exposes 19 tools. Last commit 21 Aug 2026.

Nutrition tracking by Dieta.ai. Read your food log with macros (calories, protein, carbs, fat, fiber

Uptime history 57 days of history · worst day 92%
57 days agonow
95.7%
Uptime 24h
88 of 92 checks
19
Tools
read from the server
2000 ms
Response time
average over 24h
0
Stars
last commit 21 Aug 2026

What changed 77

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 August 2026. No other catalogue keeps this.

11 Oct a tool changed version2 times that day
6 Oct a tool changed version4 times that day
5 Oct a tool changed version
3 Oct a tool changed version
2 Oct a tool changed version2 times that day
1 Oct a tool changed version
13 Sep a tool changed version2 times that day
9 Sep a tool changed version
8 Sep a tool changed version
7 Sep a tool changed version
and 67 more, back to 22 August 2026

Dieta.ai does not always answer

Over the last week it answered 97.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add dieta-mcp --transport http https://api.mcp.ai/p_dieta
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "dieta-mcp": {
      "url": "https://api.mcp.ai/p_dieta"
    }
  }
}
~/.codex/config.toml
[mcp_servers.dieta-mcp]
url = "https://api.mcp.ai/p_dieta"
.cursor/mcp.json
{
  "mcpServers": {
    "dieta-mcp": {
      "url": "https://api.mcp.ai/p_dieta"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "dieta-mcp": {
      "url": "https://api.mcp.ai/p_dieta"
    }
  }
}

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dietaai
dietaai_diabetes
Configurações/perfil de diabetes do usuário (bloco user_diabetes).
dietaai_diary
Resumo do diário (journal) de um dia, no formato YYYY-MM-DD.
dietaai_diary_logs
Linhas históricas de um track do diário (ex.: série de glicose). diaryId é obrigatório; start_range_date e end_range_date filtram o intervalo quando ambos são informados.
dietaai_diary_scheme
Definições dos itens de diário do usuário (as faixas/tracks que ele acompanha, ex.: glicose).
dietaai_foods
Consulta o log de alimentos do usuário com os macros. Use date para um único dia (YYYY-MM-DD) OU start_date/end_date para um intervalo (máx 31 dias). Retorna os itens por refeição e os totais do dia (kcal, proteína, carbo, gordura, fibra, sódio, água).
dietaai_goals
Metas nutricionais do usuário (calorias, proteína, carbo, gordura, água, fibra e metas customizadas). Compare com os totais de dietaai_foods para avaliar a aderência.
dietaai_integration
Ponte HTTP para a API oficial de um wearable ligado à conta (Whoop, Strava ou Oura). O path segue a doc do fornecedor, ex.: Whoop "v1/cycle", Strava "api/v3/athlete", Oura "v2/usercollection/daily_activity". O vínculo OAuth é feito uma vez no app Dieta.ai.
dietaai_libre_data
Dados de glicose do LibreView (Libre). Body opcional, igual ao que o app envia após conectar.
dietaai_log
Registra uma refeição enviando texto e/ou a URL de uma foto pro mesmo pipeline de IA do chat do app (reconhece alimentos e calcula macros). Pelo menos um de prompt ou imageUrl é obrigatório. É fire-and-forget (retorna aceito, o processamento é assíncrono).
dietaai_sibionics_data
Dados de glicose do Sibionics (gráfico). Body opcional, passthrough.
dietaai_sibionics_glucose
Glicose do dispositivo Sibionics. O inviteId vem do perfil do usuário, não é passado pelo cliente.
dietaai_subscription
Dados da assinatura do usuário no Dieta.ai.
dietaai_user
Perfil básico do usuário: nome, email, userId, fuso horário, idioma e data de criação.
authenticate
authenticate
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
connect
connect
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
marketplace
marketplace
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
report
report_bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
show
show_version
Show the current MCP platform and adapter versions.
toolkit
toolkit_info
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Endpoints

URLTransportStateLatencyChecked
https://api.mcp.ai/p_dieta streamable-http answering 1190 ms 7 min ago

Alternatives to Dieta.ai

same job, measured the same way
Cronometer API MCP
by rwestergren

MCP server for Cronometer nutrition tracking — food logs, diary, macros, fasting

1 508 installs/wk local only
Calories Club: AI Food Tracker
by recordo-api

AI-powered calorie tracking with photo recognition, barcode scanning, and voice logging

answering
Forkmate
by forkmate

Free AI calorie & macro tracker: tell your AI what you ate and it logs it to your private food diary

14 tools answering
Sphere
by getsphere

Log meals, check calories and macros, set up a nutrition plan, and search foods.

answering
Nutrition MCP
by akutishevsky

Nutrition tracking: log meals and macros, USDA and Open Food Facts lookups, history, app import.

answering
Kairo
by kairocalories

Calorie tracker app for ChatGPT and Claude: read meals, macros, weight and log meals from chat.

answering
Emulo
by ohad6k

Mine your AI coding session logs into a you.md profile with dated receipts, for an agent to read.

230 installs/wk local only
Splot
by splot

Persistent food journal for AI assistants. Log meals, save recipes, plan meals and track nutrition.

answering

Dieta.ai — questions

Answers built from our own checks of this server.

What can Dieta.ai do?
It exposes 19 tools, read directly from the server on our last check. Among them: authenticate, connect, dietaai_diabetes, dietaai_diary, dietaai_diary_logs, dietaai_diary_scheme and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Dieta.ai working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 92 checks got a reply (95.7%), average response time 2000 ms. The bar chart above shows every period we have measured.
How do I connect Dieta.ai?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Dieta.ai need an API key?
No. Dieta.ai completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Dieta.ai?
It answers our handshake in 2000 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Dieta.ai open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.