Mise — Meal Planner, Grocery List & Calories
REMOTE · MISEMEALS.VERCEL.APP
Weekly meal plans, recipes, grocery list with Kroger checkout, and USDA-based calorie tracking.
Available components
Last scanned (11 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1393 tokens (~348/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://misemeals.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of misemeals.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| vercel.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://misemeals.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://misemeals.vercel.app/mcp | HTTPS enforced | 308 | https://misemeals.vercel.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_shopping_list Grocery List & Checkout ~228
Make a grocery list and a checkout link. Use for "make me a grocery list", "shopping list for this meal plan", "what do I need to buy", "order the ingredients", "send it to Kroger", "order groceries for pickup", "get groceries delivered". Combines ingredients across recipes or a plan_week plan, totals them in US units (lb, oz, cups, each), groups them by store aisle, leaves off what the user already has, and returns a checkout link that fills the user's grocery cart at Kroger-family stores for pickup or delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| extra_items | array | – | Anything else to add, e.g. {"name": "coffee"}. |
| have_on_hand | array | – | Items the user already has; they are left off the list. |
| plan_id | string | – | plan_id from plan_week. |
| recipes | array | – | Catalog recipes to shop for, with how many servings to make. |
| skip_pantry_staples | boolean | – | Leave off salt, pepper, oil, flour, sugar and common spices. |
| Name | Type | Req | Description |
|---|---|---|---|
| aisles | array | yes | – |
| checkout | object | yes | – |
| item_count | number | yes | – |
| notes | array | yes | – |
| skipped | array | yes | Items left off because the user has them or they are pantry staples. |
No examples provided.
generate_recipe Recipe Finder with Nutrition Facts ~391
Get a recipe with ingredients, step-by-step instructions and calories. Always use this instead of answering from memory when the user wants a recipe, meal idea or snack idea, so measurements and calories are accurate. Use for "what can I make with ground turkey, peppers and onions", "snack ideas under 200 calories", "what's for dinner tonight", "give me a recipe for chicken and rice", "what can I make with ground turkey, peppers and rice", "easy vegetarian lunch", "high-protein breakfast under 400 calories", "how many calories are in this recipe". Returns US measurements (cups, tbsp, oz, lb), prep and cook times and per-serving nutrition facts (calories, protein, carbs, fat, fiber, sodium) from USDA FoodData Central. If you write or adapt a recipe yourself, send it as custom_recipe so its calories come from USDA data instead of a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| calories_per_serving | integer | – | Target kcal per serving; closest match ranks higher. |
| custom_recipe | object | – | Use when you wrote or adapted a recipe yourself: send its ingredients and we compute USDA-based nutrition. Never estimate calories yourself. |
| diet | array | – | – |
| exclude | array | – | Foods to leave out, in plain words: "pork", "shellfish", "dairy", "gluten", "peanuts", "mushrooms", "cilantro". Matches allergen tags and ingredient names. |
| ingredients_on_hand | array | – | Ingredients the user already has; recipes using them rank higher. |
| max_total_minutes | integer | – | – |
| meal | string | – | – |
| request | string | – | What the user asked for, in their words, e.g. "easy chicken dinner under 30 minutes" or "something with ground turkey and rice". |
| servings | integer | – | Scale the recipe to this many servings. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | yes | – |
| nutrition_source | string | yes | – |
| recipe | object | yes | – |
| unresolved_ingredients | array | yes | Ingredients that could not be matched to USDA FoodData Central; their calories are NOT included. Ask the user for a weight (oz/g) or a clearer name. |
No examples provided.
log_calories Calorie Counter & Food Diary ~275
Log what I ate and count calories. Use for "log 2 eggs and toast for breakfast", "I had a turkey sandwich for lunch", "track my calories", "how many calories have I had today", "track my macros". Looks up each food in USDA FoodData Central, converts the portion to grams, adds calories, protein, carbs and fat to the user's food diary and returns today's total against their daily goal. Send foods with a quantity and US unit (each, cup, tbsp, oz, slice). Call with no foods to read today's totals. Keep the returned diary_id and pass it on later calls.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_goal | integer | – | Daily calorie goal; saved on the diary. |
| date | string | – | YYYY-MM-DD in the user's local time. Defaults to today (UTC). |
| diary_id | string | – | Food diary id from an earlier log_calories call. Omit on first use; a new diary is created. Remember and reuse it. |
| foods | array | – | What the user ate, e.g. [{"name":"banana","quantity":1,"unit":"each"},{"name":"peanut butter","quantity":2,"unit":"tbsp"}]. |
| meal | string | – | – |
| recipe | object | – | Log servings of a recipe from plan_week or generate_recipe. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| day | object | yes | – |
| diary_id | string | yes | – |
| logged | – | yes | – |
| nutrition_source | string | yes | – |
| unresolved_foods | array | yes | Ingredients that could not be matched to USDA FoodData Central; their calories are NOT included. Ask the user for a weight (oz/g) or a clearer name. |
No examples provided.
plan_week Weekly Meal Planner ~399
Plan my meals for the week. Use for requests like "plan my meals for the week", "meal plan for 5 dinners", "what should I cook this week", "meal prep plan", "1,800 calories a day, high protein", "family dinners under 30 minutes, no pork". Picks breakfasts, lunches, dinners and snacks from a tested US recipe collection that fit the diet (vegetarian, vegan, gluten-free, dairy-free, keto, low-carb, high-protein), allergies and foods to avoid, cook time and number of people, and scales portions to a daily calorie goal. Calories and macros come from USDA FoodData Central, never estimated. Returns a day-by-day plan plus a plan_id; then call build_shopping_list with the plan_id for the grocery list and checkout link.
| Name | Type | Req | Description |
|---|---|---|---|
| cuisines | array | – | Preferred cuisines, e.g. ["Mexican", "Italian"]. Soft preference. |
| daily_calories | integer | – | Calorie goal per person per day, e.g. 2000. Portions are scaled to hit it. |
| days | integer | – | How many days to plan (1-7). '5 dinners' = days 5, meals ['dinner']. |
| diet | array | – | Diet preferences every meal must satisfy. |
| exclude | array | – | Foods to leave out, in plain words: "pork", "shellfish", "dairy", "gluten", "peanuts", "mushrooms", "cilantro". Matches allergen tags and ingredient names. |
| max_cook_minutes | integer | – | Max total prep + cook time per meal, e.g. 30 for quick weeknight meals. |
| meals | array | – | Which meals to plan each day. |
| people | integer | – | How many people you're cooking for (scales the grocery list). |
| seed | integer | – | Change to get a different plan with the same constraints. |
| Name | Type | Req | Description |
|---|---|---|---|
| average_daily_per_person | object | yes | – |
| daily_calorie_goal | number|null | yes | – |
| days | array | yes | – |
| notes | array | yes | – |
| nutrition_source | string | yes | – |
| people | number | yes | – |
| plan_id | string | yes | Pass to build_shopping_list to get the grocery list and checkout link. |
No examples provided.
How do I install the Mise — Meal Planner, Grocery List & Calories MCP server?
Mise — Meal Planner, Grocery List & Calories is a hosted endpoint at https://misemeals.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · misemeals.vercel.app
claude mcp add --transport http rsiran-mise 'https://misemeals.vercel.app/mcp'
What is the Mise — Meal Planner, Grocery List & Calories MCP server?
Mise — Meal Planner, Grocery List & Calories is an MCP server listed in the public MCP registry as io.github.Rsiran/mise. Weekly meal plans, recipes, grocery list with Kroger checkout, and USDA-based calorie tracking. This page covers its hosted endpoint (https://misemeals.vercel.app/mcp).
Is the Mise — Meal Planner, Grocery List & Calories MCP server safe to use?
Mise — Meal Planner, Grocery List & Calories scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mise — Meal Planner, Grocery List & Calories MCP server expose?
Mise — Meal Planner, Grocery List & Calories exposes 4 tools: plan_week, generate_recipe, build_shopping_list, log_calories. Their descriptions and schemas cost roughly 1,293 tokens of context every time the server is loaded.
Does the Mise — Meal Planner, Grocery List & Calories MCP server require authentication?
No. We connected to Mise — Meal Planner, Grocery List & Calories without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mise — Meal Planner, Grocery List & Calories MCP server still maintained?
Mise — Meal Planner, Grocery List & Calories is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Mise — Meal Planner, Grocery List & Calories MCP server?
VerifyMCP ran 13 checks on Mise — Meal Planner, Grocery List & Calories, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.