Dieta.ai MCP server

• authenticateFree

  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.

• connectFree

  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.

• dietaai_diabetesFree

  Configurações/perfil de diabetes do usuário (bloco user_diabetes).

• dietaai_diaryFree

  Resumo do diário (journal) de um dia, no formato YYYY-MM-DD.

• dietaai_diary_logsFree

  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_schemeFree

  Definições dos itens de diário do usuário (as faixas/tracks que ele acompanha, ex.: glicose).

• dietaai_foodsFree

  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_goalsFree

  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_integrationFree

  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_dataFree

  Dados de glicose do LibreView (Libre). Body opcional, igual ao que o app envia após conectar.

• dietaai_logFree

  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_dataFree

  Dados de glicose do Sibionics (gráfico). Body opcional, passthrough.

• dietaai_sibionics_glucoseFree

  Glicose do dispositivo Sibionics. O inviteId vem do perfil do usuário, não é passado pelo cliente.

• dietaai_subscriptionFree

  Dados da assinatura do usuário no Dieta.ai.

• dietaai_userFree

  Perfil básico do usuário: nome, email, userId, fuso horário, idioma e data de criação.

• marketplaceFree

  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_bugFree

  Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

• show_versionFree

  Show the current MCP platform and adapter versions.

• toolkit_infoFree

  Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1323ms20/20
• Tool poisoning19 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 63 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

88/100

higher than 75% of 48,255 servers

Tools

19

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

53 ms

faster than 92% of 30,031 servers

Grade history

• 2026-11-01restoreD → Ascore 88

Dieta.ai: common questions

Is Dieta.ai MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Dieta.ai safety report

How do I install Dieta.ai?

It runs remotely at api.mcp.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Dieta.ai need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Dieta.ai maintained?

The last commit was 66 days ago (2026-08-30). The latest release is v0.1.0.

Is Dieta.ai up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Dieta.ai compare with other MCP servers?

safety score 88/100 (higher than 75% of 48,255 servers); tools 19 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.