All servers / Observability / Enshape
Enshape
Read your private Enshape diary and log meals through scoped account authorization.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://enshapeapp.com/mcp · Registry name: com.enshapeapp/enshape
Score 74 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 16 / 20 | |
| Inputs explained | 8 / 15 | |
| Speed | 0 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (0.4 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: Enshape 1.1.0
- Tools offered: 14 · Parameters with a plain description: 31 of 57
- One safe, read-only test call to
get_nutrition_targets: failed (first call 0.1 seconds) - Official registry entry last updated: 2026-11-19
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
get_daily_summary0 of 1 parameter describedReturns saved daily targets, quantity-weighted logged calories and macros, signed remaining and explicit overages for a strict user-local YYYY-MM-DD date. Missing or invalid nutrition is incomplete, never zero-filled; unknown totals and remaining are null. One shared diary call. No recommendations or writes.
get_nutrition_targetsno parametersReturns only saved daily calories, protein, carbs, fat and fiber targets, with missing targets explicit. No recommendations or guessed goals. Requires meals:read and consumes one shared diary call.
get_meals0 of 3 parameters describedReturns a bounded page of the connected account’s private meals for a local calendar date, including persisted IDs and saved nutrition. When hasMore is true, nextAfterId is the afterId for the next page. Oversized entries are marked for checking in Enshape. Each page consumes one diary call.
recent_foodsno parametersReturns up to 50 recent private diary entries for the connected account, including their dates and saved nutrition.
get_nearby_meal_suggestions9 of 9 parameters describedSuggests meals at restaurants near coordinates supplied by the user, from meal combinations saved in Enshape. Returns at most 10 suggestions with restaurant address and distance, saved nutrition, serving info, component items and a nutritionSource for a later confirmed diary entry. Unpersonalized unless targets are passed, or useSavedTargets is true (saved daily targets are whole-day totals, not a per-meal budget; add date to subtract that day’s diary). Menu freshness and availability are unknown, so the user must check the official current menu. The location is used only for this search and is not stored or shared. Each call consumes one diary call from the shared allowance. Never writes to the diary.
find_foods6 of 6 parameters describedSearches Enshape by name, without a location: verified restaurant menu items and reviewed restaurant meals (optionally within one restaurant chain), plus the user’s own saved foods and recipes. Returns at most 10 items per page with a ref, per-serving nutrition, provenance and, with meal targets, Enshape’s fit score and reasons; follow nextCursor for more. A menu item is one item, not a complete meal. Restaurant data may be out of date: tell the user to check the official current menu. Log a result only after the user confirms it, with log_food_reference. Each call consumes one diary call. Never writes.
get_usual_meals2 of 3 parameters describedReturns up to 10 distinct foods the user logs most, from their newest 300 diary entries on or before a local date, ranked by meal slot (when given), how often and how recently, with the latest portion, saved per-serving nutrition and a diary ref for log_food_reference. Nothing is logged: confirm the food, portion, slot and date first. Each call consumes one diary call.
get_nutrition_trends2 of 2 parameters describedReturns per-day logged totals for up to 31 user-local dates in one consistent read, with averages over complete logged days (count stated), target-hit days when daily targets are set, and the logged-day streak ending at endDate. Unknown values stay null and never become zero; unlogged days are not zero days. Factual diary totals only, no advice. One diary call for the whole range.
update_nutrition_targets1 of 6 parameters describedChanges only explicitly confirmed daily calories, protein, carbs, fat or fiber targets for the connected account. Omitted fields are preserved. Requires separate targets:write consent, at least one whole-number target, and confirmed:true. Returns the exact saved targets read back under the account lock. No automatic recommendations, profile, micronutrient or diary changes. Each valid attempt uses one shared diary call. After an uncertain outcome read targets before repeating an explicitly confirmed patch.
log_meal5 of 14 parameters describedCreates one private diary entry for the connected account after the user confirms the portion, per-serving nutrition, local date and meal slot. Requires all five nutrition values and their source. Approved estimates are labeled. After an uncertain save, check the diary before retrying with the same requestId. Identical retries return the existing entry. Changed payloads are rejected.
log_food_reference4 of 6 parameters describedCreates one confirmed private diary entry from a ref returned by find_foods (verified menu item, reviewed restaurant meal or the user’s own food), get_nearby_meal_suggestions (combo) or get_usual_meals, get_meals and recent_foods (diary entry); own foods and diary entries need meals:read too. Enshape resolves and saves the per-serving nutrition, including micronutrients when known, and, when the grant includes meals:read, returns the saved values and totals to read back. Requires quantity, local date, meal slot and confirmed:true after the user confirms. Identical retries with the same requestId return the existing entry; a different request under it is rejected. Does not change the catalog.
delete_meal2 of 2 parameters describedPermanently deletes one private diary entry belonging to the connected account after the user explicitly confirms that exact entry. Use its saved diary ID from Enshape and verify ambiguous or stale entries before deleting. If the outcome is uncertain, check the diary before retrying with the same ID. A deleted:false result means the entry is absent and does not identify who removed it. Each valid attempt, including retries and missing entries, consumes one shared diary call. Only the private diary is affected.
request_restaurant0 of 5 parameters describedStores a restaurant request in a private moderation inbox after explicit user confirmation. Requires restaurant name, a short message, and a stable requestId; optionally a coarse town or city. Never provide precise location, private contact details or diary content. Never creates restaurants or imports menu data, and makes no promise of addition or a reply. Uses one shared assistant allowance attempt; submissions also share a stricter 3 per rolling 24 hours limit per account across web, mobile and assistants. Reuse requestId after uncertain outcomes.
get_account_statusno parametersReturns server-verified Premium status, diary tool usage, remaining Free allowance, UTC reset time and request caps for the connected account. An unavailable entitlement check reports unknown, never Premium. This lookup does not consume the diary allowance and remains subject to request rate limits. Does not sell or upgrade subscriptions.
Tested by ConnectATD. Spotted a mistake? Tell us.